Since the plist is just one small file, another way to do it might be
to drop the custom plist into the resources folder of the pkg bundle
(no paxing required) and use a postflight script to copy it into place
after the rest of the payload has been deployed the normal way.
Or, as someone else mentioned, you could target 10.4 (with the
installer package, not the application) to make the template archive
format more amenable to munging.
wp
On Jun 25, 2008, at 4:59 PM, Ryan Harter wrote:
That sounds like exactly what I would like to do, but I'm not quite
sure how to copy the plist into the package. I was looking at using
pax, but since I'm targeting Leopard, and developing on Leopard,
package maker keeps making metapackages, which pax doesn't seem to
understand, and I can't find out the equivelent of the old "Show
Package Contents."
So far it seems o be the metapackages screwing me up. Any thoughts?
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
