Apple

OK, thanks for the explanation. FYI: what I’ve been doing long since before PackageMaker started to support setting file permissions is to clean up ownership and privileges in postflight scripts. I guess I’ll just have to continue splitting forks the old way until the “original root folder preservation” process changes.

Thanks,

A. London

From: Christopher Ryan [mailto:email@hidden]
Sent: Friday, April 21, 2006 2:40 PM
To: Aaron London
Cc: email@hidden
Subject: Re: Resolution of PackageMaker CLI with Preserve Resource Forks option requiring root privs?

It isn't that Package Maker's splitting of the resource fork really requires root privs, it is that it tries to preserve the original root folder you select and make a copy (that has split resources), to do this it makes you authenticate in order to ensure the permissions of the file root will remain the same.

Unless you really do want files installed as user ID 501 (and you don't, because you never know what the user's user ID really will be), it is assumed the permissions of your files/root are set to something other then your uid, which would require root to replicate.

We are working on making this less painful, but for now you must authenticate in this situation.

Chris

Hi,

Forgive me if I missed the resolution to the discussion of this topic. Was it determined to be a bug? It seems as it should since /Developer/Tools/SplitForks does essentially the same thing and does not require root privs.

A. London

_______________________________________________

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