I'm trying to use packagemaker to bundle up our software, which previously required use of the command line to install. We do nightly builds (almost entirely automatically) and distribute those installers that don't have fatal problems, and I'd like to create the .pkg installers automatically too. I have a shell script that performs all of the necessary tasks and works well when run interactively. The call to packagemaker looks like this:
/Developer/Tools/packagemaker -build -v -p $PWD/$PKGNAME -f $PWD/app_root -i $HOMEDIR/installer/mac/Info.plist -d desc.plist
The plist files are relatively minimal, basically just a few tweaks to customize the appearance. The problem is that when run automatically, the script fails. The steps to start it are somewhat complicated:
1. An actual user starts the shell script to run the builds and tests on the master server.
2. This script SSHes into every build host using a special-purpose account, and runs the tests.
3. After the tests are done, a simple program (with permissions -rws--s--x) is run to start the installers building, using another special-purpose account.
4. The installer building is then done by a long chain of shell scripts.
In this context, packagemaker prints this out:
---
Creating Package Shell
Scanning Package Root
The package could not be created because of the following errors:
A problem was encountered with the "packagearchiver" tool.
---
And that's all the information I can get from it. No core files, nothing in the syslog. And the only mentions of this error message that I could find on Google don't appear to have been solved. Does anyone know what it might indicate, or at least how I could debug it further?
thanks,
Nat