Expected behavior for upgrades with changed file locations
Expected behavior for upgrades with changed file locations
- Subject: Expected behavior for upgrades with changed file locations
- From: Jeremy Reichman <email@hidden>
- Date: Tue, 25 Jan 2011 13:51:13 -0500
- Thread-topic: Expected behavior for upgrades with changed file locations
What is the expected behavior for upgrades of existing packages --
specifically packages in 10.4 format -- that have changed file layouts
since the last version was installed? If there is a difference in behavior
for packages in 10.4 vs. 10.5 format, I'd be interested in knowing about
that.
For example, let's say package version 2.1 installed a LaunchAgent in the
local domain, but version 2.5 no longer needs that and does _not_ come
with it in its package payload. Version 2.5 happens to install a local
domain LaunchDaemon instead. Both packages have the same ID. There are no
installer components or user choices available. Without any scripts, would
the upgrade of version 2.5 over 2.1 be expected to remove the
no-longer-in-payload LaunchAgent or not?
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.
Thanks!
--
Jeremy
_______________________________________________
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