Re: File permissions of directories created by Installer.app are wrong.
Re: File permissions of directories created by Installer.app are wrong.
- Subject: Re: File permissions of directories created by Installer.app are wrong.
- From: "Arne Scheffler (ext)" <email@hidden>
- Date: Thu, 20 Jul 2006 09:49:37 +0200
Hi Rick,
Rick Sustek wrote:
Arne,
my understanding, is that the Installer will only create directories and
files as instructed within the pax archive of a package.
All ownership and permissions are driven by the archive contents, and it
is the responsibility of the package author to set those as needed,
while constructing the package.
No, if you set IFPkgFlagDefaultLocation to something which does not
exist, the Installer will create this location, but with the wrong
permissions I think. And that's what I want to know, if this is a bug or
if we need to alter the permissions with a script after installation.
cheers
arne
-Rick
Begin forwarded message:
From: "Arne Scheffler (ext)" <email@hidden>
Date: July 19, 2006 8:31:02 AM PDT
To: email@hidden
Subject: File permissions of directories created by Installer.app are
wrong.
Hi,
suppose I got an package that installs per default into
/Applications/Some.app/Contents/Resources/A/B
If this directory structure does not exist, all non existing
directories are created with u=rwx g=rx o=rx. But the default
permissions for /Applications is u=rwx g=rwx o=rx. So I thought it
would take the permissions from the last existing parent directory to
create the new ones.
Is this expected behaviour or not ?
arne
_______________________________________________
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
_______________________________________________
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