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 el
On Jun 25, 2008, at 10: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 metapackage
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'
If the only thing that changes about the pkg is that one plist file,
you could create the pkg manually and store it as a resource. When you
want to write out the custom installer, write a copy of your pkg
template to disk and then copy in your newly-created plist file.
wp
Sent from my iPho
Thanks for the response Thomas.
What I want to do is create the pkg on the fly by the code. The setup
program has text fields for the user (in this case the lab
administrator) to set the custom preferences which my program pulls
from the plist. Now I just need to be able to construct a pl
Hi Ryan,
i have not unterstand your question completely.
Do you what to create a Installer pkg on the fly by code or do you
what to create a InstallerPackage with some custom pages and settings.
Both is possible.
I would like to help you
Thomas
Am 24.06.2008 um 01:17 schrieb Ryan Harter:
H
Hey all-
I have a helper program that essentially only needs to create a plist
for a different gui-less program. This can be done manually, but I
want a gui to aid users. What I would like, is for the user to open
this setup program, set some custom strings and other preferences, and
ha
