Re: Expected behavior for upgrades with changed file locations
Re: Expected behavior for upgrades with changed file locations
- Subject: Re: Expected behavior for upgrades with changed file locations
- From: Eli Bach <email@hidden>
- Date: Tue, 25 Jan 2011 11:57:21 -0700
On Jan 25, 2011, at 11:51 AM, Jeremy Reichman wrote:
>
> I have seen plenty of examples of installers removing (as well as adding,
> obviously) files during upgrades, but I haven't investigated whether those
> removals were driven by scripts or the package payload. I tend to see a
> lot of talk about reliance on scripts for upgrades and I want to know
> whether that is really necessary or not.
>
Yes, scripting is the way to go for doing these kind of changes.
And note that 'local domain' is much easier to do in a reasonable way from the application and not from the installer, for things like:
-multiple users
-FileVault home directories
-users created after your package was run
-remote user directories [where user folder isn't available until they log it]
-and even more!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden