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: "Glover,David" <email@hidden>
- Date: Tue, 8 Sep 2009 11:07:31 +0100
- Thread-topic: clarification re: Mac OS X standard directories inside a component's hierarchy
If your packages are built from the command line using packagemaker,
then you have to include standard Mac OS X folders inside your package
hierarchy anyway. This is because there are no build flags that allow
you to specify a destination folder.
Chances are this has changed since the last time I looked though :)
-----Original Message-----
From:
installer-dev-bounces+david.glover=email@hidden
[mailto:installer-dev-bounces+david.glover=email@hidden
le.com] On Behalf Of Iceberg-Dev
Sent: 26 August 2009 21:28
To: justin blecher
Cc: email@hidden
Subject: Re: clarification re: Mac OS X standard directories inside a
component's hierarchy
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:
etheanworld.com
This email sent to email@hidden
Promethean Limited is a company registered in England and Wales with company number 1308938 and VAT number GB 572 2599 18
______________________________________________
Promethean Ltd and or associated and or subsidiary companies :
The views expressed in this communication may not necessarily be
the views held by Promethean Ltd and or associated and or subsidiary companies.
This e-mail is for the exclusive use of the addressee(s). Unauthorised
disclosure, copying or distribution is prohibited.
This e-mail message has been swept for the presence of computer viruses.
Promethean Ltd and or associated and or subsidiary companies accepts no liability for any loss resulting from this email transmission.
Promethean, Promethean House, Lower Philips Road, Blackburn, Lancashire, BB1 5TH, UK. Please update your records accordingly. Thank you!
_______________________________________________
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