Re: incorrect packagemaker group
Re: incorrect packagemaker group
- Subject: Re: incorrect packagemaker group
- From: Dominic Feira <email@hidden>
- Date: Thu, 29 May 2008 17:48:00 -0400
It was incorrect in both locations. I did manage to figure out what
was wrong. I already had the component installed "incorrectly".
During development I lazily just drag the component into /Library/
Audio/Plug-Ins.
It turns out that packagemaker's "apply recommendations" simply copies
permissions for any paths that it can match already on the system.
Since it was able to match "MyComponent.component" it use the user/
group that already existed on the system. Once I removed the plug-in
and then created the installer again everything was fine.
This doesn't appear to documented anywhere that I've looked.
Dominic Feira / Code Monkey / Ambrosia Software, Inc. -- http://www.AmbrosiaSW.com
On May 29, 2008, at 4:53 PM, Stéphane Sudre wrote:
On May 29, 2008, at 2:13 AM, Dominic Feira wrote:
Hello,
I'm creating a package to install a component at:
/Library/Audio/Plug-Ins/Components/MyComponent.component
I have setup a pmdoc and run it via the command-line. The installer
runs fine except that the permissions on the component are
incorrect. Here is a dump of the ownership for the the resulting
package.
Library - root admin
Audio - root admin
Plug-Ins - root admin
Components - root 501 (should be root admin)
MyComponent.component - root 501 (should be root
admin)
o Is it the ownership in the pax/bom or after installation?
_______________________________________________
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