Why doesn't the Chrome installer include the license agreement?
It only says:"By installing, you are agreeing to the current Google Chrome End User License Agreement as published here: http://www.google.com/chrome/eula.html
Portableapps.com is not affiliated with Google. Google and Chrome are trademarks or registered trademarks of Google Inc."
Should I go there first and check&read the license???
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
You're agreeing to it. Lots of software simply links to it now instead of including it all in a tiny box. It's arguably easier to read. And many sites will auto-language switch the EULA based on your browser's language.
Sometimes, the impossible can become possible, if you're awesome!
I don't plan on using it so it doesn't really matter
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Maybe my question got lost in the editorializing. Sorry...
Haven't we been advised not to let portable software auto update, or is that only for Firefox?
I avoid all things Google for privacy issues, and for their insistance that they know better than me when to update my software.
In the EULA is this paragraph, standard now in all their software:
11.1 The Software which you use may automatically download and install updates from time to time from Google. These updates are designed to improve, enhance and further develop the Services and may take the form of bug fixes, enhanced functions, new software modules and completely new versions. You agree to receive such updates (and permit Google to deliver these to you) as part of your use of the Services.
In general, yes you should avoid auto-updating. Once it is released, the PortableApps Updater should handle updating, but if your app updates itself, the update may introduce changes to the program that the portable launcher doesn't know how to handle. Firefox was an example of where things got even worse, because the update actually messed up your local Firefox installation (from what I can tell, the issue HAS been resolved, despite there never being any definitive answer to that end, but the bug tracker thread seems to indicate it is fixed).
Quamquam omniam nescio, nec nihil scio.
You can't really update through GCP since the Google Chrome updater will try to install locally.
However the launcher doesn't put all the necessary registry bits in place for the updater to work anyway, just for Google Chrome itself, so it's not really an issue.
Signature automatically removed for being too awesome.