![]() Member "baraka'' was the one who first got me looking into this. The user checks the Chrome blog to see if a new version is available if it is, they then run the update script manually. ![]() Initially, I built the updater to work in tandem with manual input by the user. So this is why the specific Puppy 'Chrome-portable updater' has been developed. ![]() The normal system locations for Chrome installation don't work for us because of running-as-root and the need to run the browser as user 'spot' it basically chucks a giant spanner in the works! This is how it's designed to work for mainstream distros, where everybody is just a 'user', with dedicated home directories. Chrome updates then come down the pipe along with system updates. deb package up to install a daily cron job, which operates in tandem with a URL to a dedicated Google repo that then 'adds' a repository to your package manager. See, the 'normal' internal updater for Linux Chrome, where it updates 'in-situ' (like Firefox) has never worked the way it does under Windows & Mac. When you say "it wants to update but it of course can't", I'm going to hazard a guess that you're getting that wee red-shaded box up near the Menu 'hamburger' symbol.saying something like an update is available, but Chrome cannot update?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |