You are here

When UPdating Dev Channel PORTABLE version of Chrome..ALSO how about/how will THIS UPdating, affect the Portable STABLE v?

5 posts / 0 new
Last post
sweepsnregs
sweepsnregs's picture
Offline
Last seen: 2 years 8 months ago
Joined: 2009-11-26 00:26
When UPdating Dev Channel PORTABLE version of Chrome..ALSO how about/how will THIS UPdating, affect the Portable STABLE v?

I installed 2 portableapps.com VersionS of Google Chrome, one is the Dev Channel @ https://portableapps.com/news/2010-02-24_-_google_chrome_portable_4.0.24... (The other is the Portable STABLE Chrome version.)

So when it comes time to update the Dev Channel PORTABLE version with newer DEV CHANNEL version, will it keeps all the EXTENSIONs I installed from the older version? (How will this action, affect the Portable STABLE version?)

THANKS forward to your answer,

ottosykora
Offline
Last seen: 4 days 13 hours ago
Joined: 2007-10-11 17:48
2 different folders

hope with two different names, then when you update the first you install it into the first folder and the second into the second, so this is two different apps and can not interfere, the extensions, provided they are portable, will be in the folder of that app somewhere, so will not interfere with the other.
If some extension is non portable and will work only from hard drive and via registry or so , then this no one knows what happens.

Otto Sykora
Basel, Switzerland

sweepsnregs
sweepsnregs's picture
Offline
Last seen: 2 years 8 months ago
Joined: 2009-11-26 00:26
How do I know individual EXTENSION-level, which is PORTABLE?

So how will I know, down to the individual extension-level, which extension is portable, and which is not? Should I had even cared to ask this question? Is it when I install the individual ext? Some behavior gives it off? Is it on the ext homepage (if not stated, I would think it's a good idea to start a policy of having the authors state this on the homepage and/or alert us in a dialog box BEFORE we install that ext.)

I guess reason I'm asking is if any of us find an extension NOT portable, can we ask the author to try hard to make it portable now so we can ''bring it with us too''? Or is it not an easy matter of turning it on or turning it off but what that individual ext needs to do behind the scenes?

''so will not interfere with the other'': this applies vice versa too? Like when updating the STABLE Portable version...it effects on the DEV Channel VERSION?

dboki89
Offline
Last seen: 9 years 5 months ago
Joined: 2009-11-30 20:44
.

So how will I know, down to the individual extension-level, which extension is portable, and which is not?

You can't. Not unless you personally test out each and every one of them by checking if they are portable.

Should I had even cared to ask this question? Is it when I install the individual ext? Some behavior gives it off?

There's no "behavior that gives it off", while you're installing it. You can't tell if an extension is portable until you test it out with different drive letters (i.e: moving from one drive to another). The simplest way to test is installing an extension when the program is located in (for example):

D:\PortableApps\GoogleChromePortable\

You change some settings of that extension, save them and exit the application. Then you change the drive letter (works also for moving the entire folder structure to another drive), and then it would be something like

E:\PortableApps\GoogleChromePortable\

Now you look at whether the changes you made persist or not. If not, it's not portable. If yes, then continue testing. Now, while in a new location (E:\), change some more settings of that extension, save and exit. Now move the entire folder structure back to D:\ and check whether the settings made both the first and second time persist. If they do, it's likely that the given extension is portable. Likely, but not certain - you would need to test it out a lot thoroughly to determine with certainty.
Note: when I said move, I meant move, not copy to other drive. I could explain the reasons, but don't want to make this longer than needed.

...if any of us find an extension NOT portable, can we ask the author to try hard to make it portable now so we can ''bring it with us too''?

Well, you can always try with a polite email asking the author to try to make the necessary changes to make it portable, but sometimes it just won't help. On the other hand, never underestimate the power of persuasion! Smile

''so will not interfere with the other'': this applies vice versa too? Like when updating the STABLE Portable version...it effects on the DEV Channel VERSION?

Yes, it applies to the other way around. As long as you're not running ANY version of a software you're updating (so close both the "development test" and the "stable" versions of GCP before updating any of them), it should not be possible for one update to mess around with the other app. They are separate apps, in separate folders.

Note: The method of simple testing of the extensions' portability applies to other browsers as well. This is a simple way to test, and can be done on all portable browsers.

My posts are old and likely no longer relevant.

ottosykora
Offline
Last seen: 4 days 13 hours ago
Joined: 2007-10-11 17:48
exactly!

and if someone does all perfect, he will also run regshot before/after installation of the extension and see what it does to the local system.

Otto Sykora
Basel, Switzerland

Log in or register to post comments