Re: Installing command line tools
Re: Installing command line tools
- Subject: Re: Installing command line tools
- From: Eli Bach <email@hidden>
- Date: Wed, 4 Feb 2009 11:04:58 -0800
On Feb 3, 2009, at 11:56 PM, Eli Bach wrote:
* Is there a way to Iceberg behavior out of PackageMaker w.r.t. a
directory's contents?
Yeah, this behaviour annoys me as well (that you can't just tell it
to grab everything in a folder when it builds, instead of just the
files present when the folder is added to the package in
PackageMaker).
Offhand, I can only think of brute-forcing it in, as in, directly
editing the plist's within the pmdoc (as it's just a folder of a
couple of plists)
Just to follow up on this, PackageMaker seems to not really be
deterministic about this.
I just checked my current installer, and PackageMaker left the
"packagename-contents.xml" file within the .pmdoc virtually empty (it
only has "<pkg-contents spec="1.12"/>"). However, now when I reopen
the .pmdoc and switch to looking at the package contents, PackageMaker
will update this file with the specific contents of the folder. It
appears to only hold the listing of all the files, so you may be able
to just keep it as the empty xml tag. For me, building the package
from the command line, it seems to properly grab the contents of the
folder.
This may be the way to do it. But I've also noticed that PackageMaker
will sometimes (not always) crash if I remove the file xml entries
from it using a text editor and then opening the .pmdoc
Eli
_______________________________________________
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