So I've read the thread on why ChromePortable cannot update itself and understand that. In the thread, which was from back in April, there was mention of waiting for Portable Apps Updater, which is part of the menu now. But I've run the Updater and it finds nothing to update on Chrome6, which probably means that it only checks for updates of PA.c releases. That makes sense also. And we really can't expect the developer to keep up with Googles random and frequent updates.
Still, one more question. Is there any way a user could manually update the portable version? Could I install the Google version, copy some files over, and uninstall the Google version and get the equivalent without destroying the portable status?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
6.0.472.63 *IS* the most recent version of Chrome and, thus, there is nothing to update. Our Stable, Beta and Dev channels are all up to date. Just be sure you install them to their standard directories (GoogleChromePortable, GoogleChromePortableTest and GoogleChromePortableDev respectively) so the updater will find them.
Sometimes, the impossible can become possible, if you're awesome!
I tend to change the name of the folders to GoogleChrome6, GoogleChrome7 so that I can tell them apart. Your naming scheme is somewhat abstruse.
Generally, we have AppNamePortable and that's it. For Firefox, we added in the ability to test out alpha and beta versions, so it's called FirefoxPortableTest as they both use the same directory (which makes upgrades happy). Later, people asked about adding the same ability for Chrome betas, so we also added GoogleChromePortableTest for the betas. And later, people asked for the Dev versions, so we added GoogleChromePortableDev. If we go back and change a name, it'll cause issues with upgrading for any existing users.
If you're using the platform, there's really no need to customize directories anyway, as you're free to rename the app in the interface and it shows you the version on hover as well. If you want to have beta, stable and dev, you can do so and all will update appropriately. Since changing directories causes problems with updates, when you install an app through the platform, it automatically handles picking the directory for you.
Sometimes, the impossible can become possible, if you're awesome!
Yes, now that I know about it, I can comply. I only use the platform for its update capability. Otherwise I'm a Launchy kinda guy.
thanks.