Portable Adium and Sparkle issue

Gand · Post by **Gand** » Sat Feb 17, 2007 6:35 pm

I'm working on Portable Adium 1.0.1 r4 and is quite ready.
There is a little issue with autoupdate managed by Sparkle.
When autoupdate "Install and Relaunch", Adium, inside Portable Adium, is relaunched without custom preferences folder path.

Is there a way to solve it?

P.S. Similar issue was solved in Portable Vienna.

Post by **evands** » Sat Feb 17, 2007 7:18 pm

Well, how was similar issue solved in Portable Vienna?

Gand · Post by **Gand** » Sat Feb 17, 2007 11:22 pm

evands wrote:Well, how was similar issue solved in Portable Vienna?

Sorry I don't know exactly, is something like save path before running Check for Updates and then pulling it out again and clearing it when Adium is restarted.
I have to ask for Vienna devs collaboration to get more infos.

Post by **stevepa** » Sat Feb 17, 2007 11:42 pm

Vienna takes a -profile command line parameter that specifies the path to the profile. Just before Sparkle is about to restart Vienna, it caches a copy of the path in the preferences. On restart, it looks for this copy and uses it if it is found.

http://vienna-rss.svn.sourceforge.net/v ... iew=markup has the relevant code.

Gand · Post by **Gand** » Sun Feb 18, 2007 12:24 am

stevepa wrote:Vienna takes a -profile command line parameter that specifies the path to the profile.

Instead Portable Adium is launched by this shell commands:

Code: Select all

defaults write "$1/Contents/Resources/Adium.app/Contents/info" "Preference Folder Location" \
"$1/Contents/Resources/Library/Application Support/Adium 2.0"

plutil -convert xml1 "$1/Contents/Resources/Adium.app/Contents/Info.plist"

"$1/Contents/Resources/Adium.app/Contents/MacOS/$appid"

Where $1 is the path to "Portable Adium.app" where ever it is.

I'll try also to check out how Portable Cyberduck had solved this issue as it is launched in the same way.[1] [2]

Gand · Post by **Gand** » Mon Feb 19, 2007 2:37 am

Gand wrote:I'll try also to check out how Portable Cyberduck had solved this issue as it is launched in the same way.[1] [2]

Sorry, my mistake, by the moment only Vienna solve Sparkle issue.

This problem affect all portable apps using Sparkle. Not a great issue indeed. When you reopen again Portable app you get your portable preferences.
But as Sparkle is managed by application itself is hard to solve by portable script.

Sorry again for my mistake, as managing 24 portable apps I get a little confused.

Please let me know if it could be solved and/or if I've to fill a ticket .

Thanks.

Post by **Catfish_Man** » Mon Feb 19, 2007 2:55 am

It seems to me that this should be solved at the sparkle level, perhaps by allowing pre/post-install scripts. Since I know someone who is working on exactly that... I suspect this will not be an issue in the semi-near future.

drmoque · Post by **drmoque** » Mon Feb 19, 2007 10:14 pm

Hi,

Since I manually updated my Portable Adium 0.89 to Adium 1.0 and then recently to Adium 1.0.1, I wanted to add that the auto update did not work well for me. Adium 1.0 did tell me a new version was available. I then instructed it to updrade and it seemed to hang (taking really, really long to do anything). I had a similar problem when trying to install 1.o directly to my USB drive. I found in both cases it was easier to first install Adium to the HD and then move it to the USB drive.

BTW. So far no major problems with the manual update of 0.89 to 1.0

For those interested in how I did this, here are the steps I followed:
1.Copy my portable adium from my flash drive to my HD as a backup.
2. Mount Adium 1.0 DMG
3. Install Adium 1.0 .to my HD applications folder
4. Get Info on Portable Adium and show package contents
5. Open up Portable Adium.app/Contents/Resources/app/
6. Copy Adium 1.0 over Adium 0.89
7. Start up Portable Adium

It went very smooth. Some notes about installation. Adium 1.0 is about 29 MB and lots of small files so it did take a while to copy. Also I did attempt to install directly from the disk image to my flash drive but it was copying very very slowly which is why I installed on the HD first.

Sorry if this confuses the issue but I just wanted to share my experience.