Re: clarification re: Mac OS X standard directories inside a component’s hierarchy
Re: clarification re: Mac OS X standard directories inside a component’s hierarchy
- Subject: Re: clarification re: Mac OS X standard directories inside a component’s hierarchy
- From: Iceberg-Dev <email@hidden>
- Date: Wed, 26 Aug 2009 22:28:06 +0200
On Aug 26, 2009, at 9:45 PM, justin blecher wrote:
greetings everyone,
i'm new around these parts and currently wrestling with the concepts
and best practices for evaluating existing packages, repackaging
non-pkg installers, and rolling out InstaDMG-created images for < 30
macs i have the pleasure of [part-time] managing.
today my question centers around this quote:
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.
[...]
here's my real questions:
* is my assumption/interpretaton -- anytime there are items that
belong in a "standard directory", a separate package must be made for
them, targeted to that standard directory -- correct?
* are my evaluations and suggestions for the fixing (hah!) the
offending packages on the right track? (not like i'm interested in
fixing them, i'm just trying to grok the concepts for my own
packages.)
IMHO, this warning is just plain bullsh*t.
What you should not do (if you can) is to allow overwriting of the
permissions of these standard directories.
This somehow assumes that you are confident that no other packages
have messed with them.
* what is the definitive list of "Mac OS X standard directories", or
how can i generate it dynamically?
You could find it by examining the Essentials.pkg packages from a Mac
OS X Install Disc. Pacifist can help. _______________________________________________
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