• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: clarification re: Mac OS X standard directories inside a component’s hierarchy
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: justin blecher <email@hidden>
  • Date: Wed, 26 Aug 2009 18:52:40 -0400

On Wed, Aug 26, 2009 at 4:28 PM, Iceberg-Dev<email@hidden> wrote:
>
> On Aug 26, 2009, at 9:45 PM, justin blecher wrote:
[...]
>>  * 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.

ooookay. care to elaborate why you feel that way? :)


> 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.

right. well, by default the packages i'm creating in Iceberg don't
have "allow overwriting of permissions" on, so i shouldn't have to
worry about that, right?

are you suggesting that it doesn't matter what the
owner/group/permission bits are on any of the enclosing folders if
they already exist? i'd expect for consistency/sanity's sake that one
would want to make the permissions of the enclosing folders the same
as what currently exists [on a reference system].

what if other packages were sloppy and messed with the perms (they had
enclosing folders set to incorrect perms and enabled 'allow
overwriting...')? just hope that the user will eventually run "repair
permissions"?


>>  * 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.

ok, got it. i ended up using good 'ole lsbom:

  lsbom -p MUGsf `pkgutil --bom /Volumes/Mac\ OS\ X\ Install\
DVD/System/Installation/Packages/Essentials.pkg` | grep '\./Library/'
| grep ^d > essential_directory_listing.txt

...and then manually filtered the resulting list to get:

drwxrwxr-x 	root	admin		./Library/Address Book Plug-Ins
drwxrwxr-x 	root	admin		./Library/Application Support
drwxrwxr-x 	root	admin		./Library/Application Support/Apple
drwxrwxr-x 	root	admin		./Library/Application Support/Macromedia
drwxrwxr-x 	root	admin		./Library/Application Support/Mozilla
drwxrwxr-x 	root	admin		./Library/Application Support/ProApps
drwxrwxr-x 	root	admin		./Library/Audio
drwxrwxrwt 	root	admin		./Library/Caches
drwxrwxr-x 	root	admin		./Library/ColorSync
drwxrwxr-x 	root	admin		./Library/Components
drwxrwxr-x 	root	admin		./Library/Compositions
drwxrwxr-x 	root	admin		./Library/Contextual Menu Items
drwxrwxr-x 	root	admin		./Library/Dictionaries
drwxr-xr-x 	root	wheel		./Library/Filesystems
drwxrwxr-x 	root	admin		./Library/Fonts
drwxrwxr-x 	root	admin		./Library/Frameworks
drwxrwxr-x 	root	admin		./Library/Image Capture
drwxrwxr-x 	root	admin		./Library/Input Methods
drwxrwxr-x 	root	admin		./Library/Internet Plug-Ins
drwxr-xr-x 	root	wheel		./Library/LaunchAgents
drwxr-xr-x 	root	wheel		./Library/LaunchDaemons
drwxrwxr-x 	root	admin		./Library/Logs
drwxrwxr-x 	root	admin		./Library/Mail
drwxrwxr-x 	root	admin		./Library/Modem Scripts
drwxrwxr-x 	root	admin		./Library/PDF Services
drwxrwxr-x 	root	admin		./Library/Perl
drwxr-xr-x 	root	wheel		./Library/PreferencePanes
drwxrwxr-x 	root	admin		./Library/Preferences
drwxr-xr-x 	root	admin		./Library/Preferences/SystemConfiguration
drwxrwxr-x 	root	admin		./Library/Printers
drwxrwxr-x 	root	admin		./Library/QuickLook
drwxrwxr-x 	root	admin		./Library/QuickTime
drwxrwxr-x 	root	admin		./Library/Ruby
drwxrwxr-x 	root	admin		./Library/Screen Savers
drwxrwxr-x 	root	admin		./Library/Scripts
drwxrwxr-x 	root	admin		./Library/Security
drwxrwxr-x 	root	admin		./Library/Spotlight
drwxr-xr-x 	root	wheel		./Library/StartupItems
drwxrwxr-x 	root	admin		./Library/Updates
drwxrwxr-x 	root	admin		./Library/User Pictures
drwxrwxr-x 	root	admin		./Library/WebServer
drwxrwxr-x 	root	admin		./Library/iTunes

... which is good enough to guide me in setting the perms in my
enclosing folders (if i choose to do so... still researching this).


-justin
 _______________________________________________
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

  • Follow-Ups:
    • Re: clarification re: Mac OS X standard directories inside a component’s hierarchy
      • From: Iceberg-Dev <email@hidden>
References: 
 >clarification re: Mac OS X standard directories inside a component’s hierarchy (From: justin blecher <email@hidden>)
 >Re: clarification re: Mac OS X standard directories inside a component’s hierarchy (From: Iceberg-Dev <email@hidden>)

  • Prev by Date: Re: clarification re: Mac OS X standard directories inside a component’s hierarchy
  • Next by Date: Re: 10.6 Upgrade kills permissions on Application Support folder for my app
  • Previous by thread: Re: clarification re: Mac OS X standard directories inside a component’s hierarchy
  • Next by thread: Re: clarification re: Mac OS X standard directories inside a component’s hierarchy
  • Index(es):
    • Date
    • Thread