For some reason, I can’t get the iLife Support 9.0.2 update to stick in my builds. Is there any special magic I need to do? (e.g., precede it with iLife 9.0.1, place it at the end of the other updates)
I noticed that too. Something is messed up with the update, I managed to make it work by booting the system, choose download only to fetch the new iLife update, then put that one in the build.
Recently I’ve tired of maintaining all these updates, I’m now creating images from golden masters and scripting my changes through Deploystudio and found it to be a much better approach.
InstaDMG is good for creating a base image for the golden master.
I was hoping that putting things in a chroot jail would solve this issue, but it looks like distribution scripts in a flat-package (like the iLifeSupport9.0.2 .pkg) escape the chroot jail. I am going to file a bug on this. But the solution to it is to use a InstallerChoices.xml file that chooses all of the packages inside the update. That should solve the problem. Until then I have a new bug to write up with Apple.
The trick is that you probably don’t have that update on your booted OS. The whole problem here is that the Distibution script is looking at the base OS and making decisions on what to install based on what it finds there, rather than looking at the target disk. It is doing this even though it’s (sort-of) parent process is running inside a chroot jail that means it should not be able to see the host OS.
Comments are closed