Re: PackageMaker automation
Re: PackageMaker automation
- Subject: Re: PackageMaker automation
- From: Dan Spirlock <email@hidden>
- Date: Wed, 10 Dec 2008 09:40:33 -0800
I've gotten that crash before as well. One thing I've had success with
is rather than calling the PackageMaker command line utility, which is
just an alias to the PackageMaker binary in the app bundle, invoke the
PackageMaker executable binary directly:
/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/
PackageMaker --doc some.pmdoc
Hope that helps
- Dan
On Dec 10, 2008, at 8:35 AM, Everette Clemmer wrote:
Yeah it looks like using the --doc flag with a .pmdoc file is still
broken.
If I understand the man page correctly, the following should output a
package file in the same directory as the input .pmdoc file:
packagemaker --doc some.pmdoc
Instead I get the following stack trace which seems to indicate that
there's
a problem in the command line packagemaker's interpretation of one
of the
arguments in the .pmdoc xml. The same .pmdoc file works like a charm
when
run from the GUI.
$ packagemaker --doc 3.3.5Patch.pmdoc
2008-12-10 11:29:12.940 PackageMaker[77957:10b] Setting to : 0 (null)
2008-12-10 11:29:12.943 PackageMaker[77957:10b] Setting to : 0
com.foo.bar
2008-12-10 11:29:12.945 PackageMaker[77957:10b] relocate: (null) 0
2008-12-10 11:29:12.946 PackageMaker[77957:10b] *** Terminating app
due to
uncaught exception 'NSInvalidArgumentException', reason: '***
-[NSXMLDocument initWithXMLString:options:error:]: nil argument'
2008-12-10 11:29:12.946 PackageMaker[77957:10b] Stack: (
2533658955,
2518863419,
2533658411,
2533658474,
2448842100,
453375,
447724,
436213,
435514,
9990,
9922
)
Trace/BPT trap
On 12/1/08 5:16 PM, "Rick Cochran" <email@hidden> wrote:
Iceberg-Dev wrote:
On Dec 1, 2008, at 4:00 PM, Everette Clemmer wrote:
Hi all,
I’m trying to set up a CI environment where one step involves
building
an installation package via package maker. I’m fairly familiar with
creating packages in the PM GUI and can create basic packages via
the
command line. I’m curious about what seems to be a vast disconnect
between the options available in the GUI compared to those
available
on the command line; the latter of which appears to be very feature
poor from the man page description. I’ve done quite a bit of
searching
in the ADC docs and on Google only to come up very frustrated.
Documentation is scarce at best and what is out there tends to be
in
excess of three years old. Does anyone on this list know of any
current, up to date, documentation on the command line
functionality
of packagemaker? I’m specifically interested in setting
installation
requirements. I’d also love to see some example scripts using it if
anyone has them lying around.
AFAIK, the command line version of PackageMaker accepts PackageMaker
project as input. So it's as rich as the UI version.
My experience is that this doesn't work. As I remember, PackageMaker
crashed.
-Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
om
This email sent to email@hidden
_______________________________________________
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
_______________________________________________
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