[Sparkle] Sparkle Integration Questions - Customized Applications

[Dean Shavit]

on 1/27/08 4:42 PM, Christopher Atlan at catlan at restoroot.com spake:

> Am 27.01.2008 um 19:25 schrieb Dean Shavit:
> 
>> 2) Sparkle replaces the entire app directory, not just the
>> differences between the update and the existing app - which won't
>> work for our users, and there's customized graphics inside the
>> application and a custom plist
> 
> What if you save all changes of the app also in (~)/Library/
> Application Support/yourapp/customization and check on startup if you
> need to copy back the customization from Application Support?
> 
>> so now to try the trunk version and a .pkg file....
> 
> 
> It is possible to handle this with *.pkgs, but I think pkgs will be
> more painful.

This is what I'm considering, but it has some unique issues, I'd rather
handle caching the personalization files at the time of update in /tmp. But
I want to try a .pkg first.

Could you explain why it would be painful? I am of the mind that it would be
quite trivial.