Re: Apple Software Delivery Guide...
Re: Apple Software Delivery Guide...
- Subject: Re: Apple Software Delivery Guide...
- From: Don Montalvo <email@hidden>
- Date: Fri, 20 Nov 2009 14:10:45 -0600
Eli Bach <email@hidden> wrote:
> On Nov 20, 2009, at 9:00 AM, Don Montalvo wrote:
>
>> Is there a a reason for this:
>>
>> "Important: Never include Mac OS X standard directories inside a component‚s hierarchy. That is, do not reflect any standard part of the Mac OS X file system (in any of the file system domains) inside your component‚s structure."
>>
>> From this URL:
>>
>> <http://developer.apple.com/mac/library/documentation/DeveloperTools/Conceptual/SoftwareDistribution/Component_Packages/Component_Packages.html#//apple_ref/doc/uid/10000145i-CH7-SW1>
>>
>> What's the reason for this? I ask because I'm used to gathering all components into a folder structure mirroring the target directories, when building a package installer.
>
> Because Installer.app will change ownership/permissions on all folders referenced in a package to what is specified in the package. So if you don't get them exactly right, you'll negatively affect the security of the user's computer. And it makes it more difficult for Apple to change ownership/permission on these folders if they need to.
But if a folder already exists, /usr/sbin/installer should leave permissions alone, correct?
> Of course, it's way easier just make a single package holding everything, instead of multiple packages, but it seems that Apple is trying to drive everybody away from using packages by making package creation, um, non-trivial.
>
> Eli
That's scary. The package creation process is pretty smooth. I hope they don't make the ride too bumpy. :)
Don _______________________________________________
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