Re: Meta-packages
Re: Meta-packages
- Subject: Re: Meta-packages
- From: Rick Sustek <email@hidden>
- Date: Thu, 6 Jul 2006 12:52:53 -0700
Could you elaborate on "bombs out"?
Try adding the "-verbose" flag on the 'installer' command line, and
perhaps it will give some useful clues.
Look at the system log for output from the installer.
Try printing (or echoing) the value of "$1" from your script, prior
to the invoke of 'installer', to ensure it is correct.
I've run some tests, using CLI 'installer' and GUI 'Installer.app'
with a couple of packages and metapackages, installing to the system
disk, and installing to other volumes. And even added spaces to the
names of other volumes. But have not had any failures at all.
I've not run a test from a system that was network booted, however,
so it is certainly possible that is THE factor.
Also, you say you have success running the GUI 'Installer.app' after
the netboot, but how about manually invoking the CLI 'installer' with
the same arguments that you use from within the script?
Double checked that each package within the meta is flagged to not
require root volume, and is relocatable? (shouldn't be an issue,
since the GUI version does the job)
Moon phases?
Good luck!
-Rick
_______________________________________________
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