So I compiled another launcher from the script in source, and I'm using it to create effectively a second instance of chrome portable, this way I have one web browser that's using a socks5 proxy that's being passed to it through the additional parameters in the googlechromeportable.ini and the other that doesn't use a proxy at all. Now after every update I have to copy my modified appinfo.ini back to the appinfo folder, but should I be recompiling the launcher every update as well?
if your using 2 launchers (GoogleChromePortable.exe and, say, GoogleChromePortable2.exe), then no. But if it's just one (GoogleChromePortable.exe), then yes because the installer overwrites the launcher.
I am using two launchers yes, I wouldn't know how to get that functionality with one. I was just wondering if in general the updates would make changes to the launcher. If that were the case should I not take the new source and recompile with my changes? Or would such updates be minimal enough that I could disregard?
Every now and then a portable app update has a changed launcher (like this) either for bugs or because a new version of the base app makes different changes to the system.
As long as the launcher you've compiled is named something different then GoogleChromePortable.exe, you need'nt worry about it too much, though. If you're really worried, just take the md5 some of GoogleChromePortable.exe and then compare it with the upgraded version to see if you need to implement the changes you've made into the new launcher.
I'd personally just change appinfo.ini and not worry about it unless Chrome starts acting funny.
Thanks a bunch. Makes sense to me, I wasn't really too worried about it but I wanted to ascertain if perhaps there was something I should be worried about. I'll update the launcher this time but won't really worry about it in the future unless chrome starts acting funny like you said. Thanks again.