RE: Preinstall/Postinstall actions not created using CLI packagemaker
RE: Preinstall/Postinstall actions not created using CLI packagemaker
- Subject: RE: Preinstall/Postinstall actions not created using CLI packagemaker
- From: "Ben Staveley-Taylor" <email@hidden>
- Date: Tue, 5 Jan 2010 09:05:56 -0000
- Organization: Oracle
Hi Paul
It's been a while since I struggled with this and things might have improved
since then, but I never got CLI packagemaker to work well for me. I suffered
a litany of problems where the output package was simply wrong,
localisations were ignored, or the .pmdoc settings (e.g. the "allow
relocation" setting) would mysteriously get reset to their defaults. I'm
sure there's a trick to fixing these problems, but I could never trust the
output of my builds.
In the end I switched to using Iceberg for my installer building, and it was
much more reliable. Like packagemaker, it is possible to run it from the
command line in an automated build. I'd recommend it if you haven't already
come across it.
-- Ben.
-----Original Message-----
From: Paul Forgey [mailto:email@hidden]
Sent: Tue 05 January 2010 01:37
To: Ben Staveley-Taylor
Cc: email@hidden
Subject: Re: Preinstall/Postinstall actions not created using CLI
packagemaker
Actions do not seem to work with command line built packages in this version
of packagemaker (and still happening in XCode 3.2.1).
I, too, would like to know if anybody has found a workaround for this.
On Sep 9, 2009, at 5:04 AM, Ben Staveley-Taylor wrote:
> I am running packagemaker from XCode 3.1.2.
>
> I have created a .pmdoc for my installer, and defined some preinstall and
postinstall actions in the Actions tab of the overall Distribution package
(not an individual package).
>
> When I build the installer from the GUI, it all works. When I build it
from the command line as I would do in a build script, the preinstall and
postinstall actions do not run. The difference is that when built from the
CLI, the pseudo-packages that contain the actions just aren't being created.
>
> Interactively built from PackageMaker GUI, I get this package structure:
>
> MyInstaller.mpkg
> Contents
> Packages
> MyPackage.pkg
> MyPackagePostflight.pkg
> MyPackagePreflight.pkg
>
> Built from packagemaker CLI tool, I get this package structure:
>
> MyInstaller.mpkg
> Contents
> Packages
> MyPackage.pkg
>
> My packagemaker command line is:
>
> packagemaker --doc "<path to MyInstaller.pmdoc>" \
> --out "<path to MyInstaller.mpkg>" \
> --id com.mycompany.myproduct.pkg \
> --verbose
>
> Has anybody else come across this? What's the vital command line parameter
I am missing?
>
> Thanks
>
> Ben Staveley-Taylor
> Oracle
>
_______________________________________________
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