Run-as-spot "$HERE/chrome/chrome" -user-data-dir=$HERE/PROFILE/spot/google-chrome -disable-infobars "$HERE/chrome/chrome" -user-data-dir=$HERE/PROFILE/spot/google-chrome -disable-infobars pretty well, I think. Mkdir "$HERE/PROFILE/spot/google-chrome" 2> /dev/null INSTALLED_VERSION=`cat "$HERE/PROFILE/spot/google-chrome/Last Version"` # Launcher for 'portable' Google Chrome browser The 'MenuReadMe' explains what to do with the Menu scripts. Click to enter, click 'LAUNCH' to, well, launch it. )ĭ'l unzip place it anywhere you like, outside the save. You'll be able to do it ALL from the Menu.Īs stated above, this will hopefully be the final, 'self-maintaining' release of Chrome-portable for the forseeable future. If you decide to add a Menu entry, you'll now also get one for the updater, beside it.obviating the need to have to go into the portable to run it. Timings have also been adjusted, so the whole thing runs somewhat quicker now.Īs before, if you want to keep the thing completely portable, just run the scripts from the portable directory as normal. deb direct to /tmp, as opposed to the portable directory FIRST, followed by a move. If it does exist, everything proceeds as normal.Ī wee bit of additional research into wget has shown me how to download the. If the download is not there, a GTK-dialog banner comes up warning the download has failed, and advising the user to try again later.followed by exiting. deb file does in fact exist in /tmp before processing begins. The updater script has had an error-check added to ensure the downloaded. You can find it at the usual link in post #1, as always. Following Oz's (and baraka's!) mention of a download-failure check - which IS a good idea, TBH - here's what will hopefully be the final issue of the portable for a while.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |