Re: Permissions - OS 10.3.7 - PackageMaker
Re: Permissions - OS 10.3.7 - PackageMaker
- Subject: Re: Permissions - OS 10.3.7 - PackageMaker
- From: Stéphane Sudre <email@hidden>
- Date: Sat, 3 Sep 2005 00:22:39 +0200
On vendredi, septembre 2, 2005, at 11:32 PM, Pavol Markovic wrote:
On Aug 31, 2005, at 10:53 PM, Peter Bierman wrote:
If you insist on packaging existing system directories into your
package, then you'll have to be sure that you get the owners, groups,
and permissions correct on those directories. And if Apple changes
them (or any other developer doing the same thing), then there will
be inconsistencies, and users will need to use repair permissions
(which more or less just looks at Apple packages to settle the
disagreements.)
So what's the purpose of "Overwrite Directory Permissions" checkbox in
PackageMaker?
This doesn't make sense for me.
To overwrite directory permissions.
It may not work if the requested privileges are not the proper one.
This option shall probably not be used if:
- you're not 100% sure about the permissions
- the archive files are relocatable (because you can't be sure the
final location is the one you think it is).
Another reason not to use it even if you know what you're doing is that
the team responsible for the directory permissions of Mac OS X is
playing a funny game which consists to change the permissions of some
common folders without any warning between 2 major releases: for
instance in Mac OS X 10.4, the /Library folder now has a sticky bit
which it didn't have before. In Mac OS X 10.3, items in StartupItems
were not all root and wheel, now they need to be, etc...
If you're not 100% sure about what you're doing, you should not be
using it IMHO.
My $0.02
_______________________________________________
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