site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com -Greg On Feb 9, 2009, at 9:47 AM, Brent Burton wrote: On Mon, Feb 9, 2009 at 10:14 AM, Greg Neagle <Greg.Neagle@disneyanimation.com> wrote: On Feb 8, 2009, at 7:18 PM, Brent Burton wrote: Hence my "This is reasonable behavior, but is a bit too loose." comment at the end of that paragraph. My point being, the results you get if you do it this way may not be the values you want at install time. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... I guess this behavior is totally expected to me because the classic way of creating a package was to create a "fauxroot" directory, place all your files and directories within, make sure they all had the permissions, owners, and groups you wanted, and pass the "fauxroot" directory to packagemaker (or even pax!). packagemaker/pax would just archive the files as-is. Basically, PM will indeed expand a directory when the package is built. The limitation is that for any file that is expanded that was not listed in the .pmdoc, PM will use the filesystem's mode & ownership. What else could it possibly use? Without any information to the contrary, the current mode, owner and group must be assumed to be correct... This email sent to site_archiver@lists.apple.com