Avoiding pmdoc files and the GUI
Avoiding pmdoc files and the GUI
- Subject: Avoiding pmdoc files and the GUI
- From: Oliver Buerschaper <email@hidden>
- Date: Fri, 11 Jul 2008 16:45:20 +0200
Dear packagers,
due to the buggy GUI version of PackageMaker 3 I'm resorting to the
command line utility in order to build my packages. I'm also trying to
avoid those pmdoc files completely because they are regularly
corrupted by the GUI.
That said, this is how far I've come without the GUI. The command
packagemaker --root payload --id com.example.MyTools --version 1 --
scripts scripts --target 10.5 --domain system --out MyTools.pkg --
verbose
successfully builds my package. Here "payload" contains a huge number
of files and folders (owned by root:wheel) I want to be deployed at /
usr/local/MyTools. The folder "scripts" contains a single file called
postinstall.
There are a couple of issues now:
1. How can I specify the destination path /usr/local/MyTools?
Obviously the installation fails because Installer doesn't know that
this is where I'd like my payload to be dropped …
2. How can I add a little descriptive text to be displayed in the
Installer's welcome window?
3. How can I check for the existence of a file on the target volume
prior to installation? The man page of packagemaker tells me this
could be done with a script called InstallationCheck, however, I have
no clue about its content and where to place this script.
4. How can I build a package with several installation choices? My
understanding is that I'll need a metapackage for this … but how to
assemble it on the command line?
Helpful comments and suggestions most welcome ;-)
Many thanks,
Oliver _______________________________________________
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