On May 6, 2008, at 2:59 PM, Peter Bukowinski wrote: On 5/6/08 2:49 PM, "Rusty Zink Myers" <email@hidden> wrote:
Yeah, I can get iLife on an instaDMG workflow fine, but the problem there is that it creates another image to deploy, not a networked leopard installer disc that I can use to upgrade or archive and install. If I used parts of the InstaDMG script, I could use SIU to create a netinstall of the leopard installer, then target disk mode the newly updated machine and then run iLife installer. Or I could house the iLife installer on a file share. Or use ARD to do it, but these all require another step that I have to start, hence defeating the automation part that I'm gunning for.
I suppose I could try to script it so the updated machine, at first boot, downloads and installs the iLife package, but, isn't that what SIU is for!
A little more info, I can use other packages I created, like firefox, to install with the SIU, but why not iLife?? I guess I could re-package it, but come on, where is the fun in that!
I had the same issue when I was trying to include Xcode 3 in my Leopard upgrade NetInstall set. SIU does not like metapackages. I haven’t gotten around to automating the Xcode install, so I just do it after the reboot. It’s not too inconvenient (yet), since I’m only trickling Leopard out at the moment.
--
Peter M. Bukowinski
IT – Sr. Support Engineer
Janelia Farm Research Campus
Howard Hughes Medical Institute
Here's the weirdest part about it, when I add ilife to the SIU workflow, and use the choose pacakges to install command, I can check iLife and choose to install it! But it then unchecks when I'm I installing leopard to the actual machine over netboot.
I am creating my third image now with Leopard, iLife 08, Firefox. Also with SUS pointer and ARD kickstart running with launchd items. Hopefully the third time's the charm... |
