Re: insufferable PackageMaker permissions defects
Re: insufferable PackageMaker permissions defects
- Subject: Re: insufferable PackageMaker permissions defects
- From: Xochitl Lunde <email@hidden>
- Date: Mon, 14 Jun 2010 08:59:04 -0500
I know that you have already switched
to Iceberg, but the trick is that you have to set your payload permissions
in the file system, NOT in PackageMaker. If you want your permissions
to be correct you can't use that permission setting thing because it loses
it's settings every time you close the program ( at least the previous
version ) and if I remember right it didn't work at all anyway. I swear
this was documented somewhere, but it wasn't easy to notice. I don't
know why they put that non-functional permission settings thing in there.
Maybe it works in the latest version, but it sounds like it doesn't
to me. You should chown -R and chgroup -R your entire payload before
building with PackageMaker. If I figure out where I saw that doc,
I'll let you know, but it's been several months now since I also have switched
to Iceberg. :)
<installer-dev-bounces+xochitl_lunde=email@hidden>
wrote on 06/11/2010 08:22:29 PM:
> 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:
> 40tripplite.com
>
> This email sent to email@hidden _______________________________________________
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