Metapackage changes ownership of sub packages?
Metapackage changes ownership of sub packages?
- Subject: Metapackage changes ownership of sub packages?
- From: Ron Aldrich <email@hidden>
- Date: Wed, 13 May 2009 18:18:40 -0700
Hello Folks,
I'm using PackageMaker 3.0.3 to create a metapackage, and I'm having a
bit of trouble getting to leave the ownership of its sub packages alone.
The sub packages are generally set to root/admin ownership, and work
correctly before they are reprocessed while creating the metapackage.
However, once I combine them into a metapackage (with embedded
subpackages) using PackageMaker, the ownership of of files within the
package get changed (ususally to user/501) privileges.
I've tried selecting the "Contents" tab of each subpackage in the
metapackage.pmdoc, and fixing the ownership there, and this looks like
it should fix the problem, but when I install the metapackage, the
ownership of the resulting files are incorrect (user/admin instead of
root/admin).
I've also tried building the package with the --no-recommend option,
but this doesn't seem to have any effect on the problem.
The target operating system is set to 10.4.
Any thoughts?
Thanks,
Ron Aldrich
Software Architects, Inc.
_______________________________________________
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