insufferable PackageMaker permissions defects
insufferable PackageMaker permissions defects
- Subject: insufferable PackageMaker permissions defects
- From: G S <email@hidden>
- Date: Fri, 11 Jun 2010 18:22:29 -0700
Am I overlooking something, or is this thing just hopelessly broken? This is the substance of my bug report. If anyone has any insights on this, I'd love to hear them. Thanks.
SUMMARY
When a PackageMaker project specifies the creation of a directory structure, the directories are assigned nonsensical and inaccessible owners and permissions.
STEPS TO REPRODUCE
Create a PackageMaker project that calls for a file to be deposited several directories below one that exists on the target volume. Do something like what our project is trying to do, as follows.
A path that's guaranteed to exist when the latest Final Cut Studio is installed is
/Library
Application Support
ProApps
Our installer is set up to put OUR.PlugIn in
/Library
Application Support
ProApps
MIO
RAD
PlugIns
When we build our PackageMaker project, the OUR.PlugIn file is sitting in the directory that holds our PackageMaker project; it's not sitting under a dummy directory structure that mirrors the structure on the destination. The documentation shows that what we're doing is correct (although the documentation is missing half of PackageMaker's UI and functionality).
The destination path for OUR.PlugIn in PackageMaker is /Library/Application Support/ProApps/MIO/RAD/PlugIns
The owner and group for our payload files are set to root:admin in PackageMaker.
EXPECTED RESULTS
The installer must create the MIO, RAD, and PlugIns directories. I would expect them to inherit the permissions of the parent (ProApps) directory. Failing that, I would expect them to inherit the permissions of the payload that's being delivered (OUR.PlugIn). At the very, very least I'd expect them all to have the same owners and permissions.
ACTUAL RESULTS
The intermediate directories are created with incorrect, differing, and in one case inaccessible permissions. Here's how they wind up:
ProApps (root / admin; root:read/write admin:read/write, everyone: read only)
MIO (root / wheel; root: read/write, wheel:read only, everyone: read only)
RAD (root / wheel; root: read/write, wheel:read only, everyone: read only)
PlugIns (ME / wheel; ME: read/write, EVERYONE: NO ACCESS)
OUR.PlugIn (root / admin; root:read/write admin:read/write, everyone: read only)
As you can see, the payload directory itself has the correct permissions, but all the parent levels between it and the target directory ARE WRONG.
THIS BREAKS OUR APPLICATION.
_______________________________________________
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