All the other 'clones'.Iron, Opera, Vivaldi, Yandex, etc., are happy to run as the "root" user.and GMail log-in isn't an issue with them. However, having said that, it must be an issue specific to Chrome/Chromium's code-base. For my own use-case, it makes no difference although I've had a GMail a/c for many, many years, I never access it via the web-interface.always via Thunderbird, so in that respect it's not affected. I confess, I hadn't really thought things that far through, i.e., with regard to GMail, etc. It works, though.so this will be the standard layout for this particular 'portable' browser from now on.ĭownloads, and MD5 checksums, will from now on always be available from this URL:-Īny 'issues', y'all know where to find me. Instead of a 'PROFILE' directory - Chrome turns its nose up at this, seemingly - it's now the standard /spot/.config/google-chrome (except that it's all self-contained). And I doubt anybody particularly wants to carry that around with them.Ĭhrome-portable now contains its own, dedicated, mini-'spot' directory, along with all associated permissions, etc. However, in 13 years of using Chrome, I've never seen anything in here.and even if it were, it would only be bug-report-type stuff for Google themselves. The 'Crash Reports' directory, in /spot/.config/google-chrome. It will create one single item in 'spot'. So I've carefully worked out what needs to run as 'spot', and what doesn't.and, making use of Fred's 'readlink' trick from the Firefox portables, Chrome now basically sets its own permissions as it goes along. (The 'normal user' thing, y'know?) This being the case, every related thing has to have spot permissions.even sym-links, believe it or not! Chrome is the only one - aside from its 'parent' Chromium, that is - that point blank refuses to run as anything other than spot. Try as I might, I couldn't see a way round this. This is the start of the regular 'portable' release threads.and it's rather appropriate that it should be the one that really got me interested in the concept all those months ago.Ĭhanges, alterations, etc, can be found at the Google Chrome 'blog':-įollowing a fair bit of head-scratching and experimenting/suck-it-and-see type stuff, Google_Chrome-portable finally is truly 'portable'.Įarlier versions insisted on putting all the config & cache stuff into the /root/spot directory.
Download google chrome portable download#
The permanent download URL for Chrome-portable will be found at the bottom of THIS post.
PLEASE NOTE: For details about the newest/current release, please always refer to the last post in the thread (or thereabouts).
Download google chrome portable portable#
There's a limit to how much I can build into the portable before the size becomes prohibitive.and it's awkward trying to cater for an OS that I don't use myself. Slacko users will have to load the devx just for the duration, then unload afterwards.
The ones I've provided for are the most commonly-used 'buntu-based Pups.
I apologise for the fact that this doesn't cater for every single Puppy out there, including the percentage of Puppy users who swear by the Slackos as their daily driver. However, to save needing to load/unload the thing just for the updater, I've now included versions of 'ar' and its single dependency for Tahrpup, Xenialpup, Bionicpup & Fossapup, built-in to the portable. Normally, this is found within the devX SFS package that comes with every Pup. FOR YOUR INFORMATION :- Please note that for the new updater script in current versions of Chrome-portable to work, the 'ar' utility is required.
0 kommentar(er)
