InstaDMG rev 202

[spaceout]

I have been using InstaDMG 1.4b4 for quite a while but have recently run into issues some others have seen, such as with the 10.5.7 combo update not being fully applied to the target disc. I updated my InstaDMG to SVN 202 (per the version number in the script file) and have been able to get the 10.5.7 Combo update applied successfully. It seems now that two other packages are now not installing. Both the latest iLife support update and the new Safari 4 package do not install and fail. Could this be an issue with the chroot/jails we are using for the package installs now? I see a section in the script where you exclude the createuser package from the jailed using the following: CHROOT_EXCLUDED_CODES=(“edu.uc.daap.createuser.pkg”) Would it help to add the two problem installers to that? How would i find out what the package identifier is for them? Would i seperate them with commas or do i create another line? Another thing i noticed, and i am not sure if this is a result of the above packages not installing, but in the console logs on a freshly imaged machine i can see usbmuxd keeps exiting with status code 1 and restarting every few seconds. Any help would be muchly appreciated!

[larkost]

The problem with the iLife support update (and I suspect safari 4, but have not checked) is that they use Distribution scripts, and the installer program runs those outside chroot jails (even when run inside one). So it is actually checking what is on your host os, rather than checking what is in the target disk. So if you have already installed these things on the host OS the installer thinks it should install nothing.

I think (but have not had time to validate) that you can use an InstallerChoices file to get around this. Right now my hands are a little full (I just got laid off, am working on a coding portfolio, and am working on InstaDMG 2.0), but will get around to trying that in the near future.

And I am trying to come up with a generic way to prevent this class of problem, and have already filed a bug on this with Apple (as well as talking with one of the product managers at Apple who might be able to put some weight on this problem), and the only solutions might be for Apple to solve it, or for me to do some fancy-footwork with re-writing installers on the fly (I don’t have a good route on that one yet).

However, I do have an idea on a technique that would at least make these sort of problems show up as an error in the build process, rather than being left to discover in Q/A on the image.

[spaceout]

So could a potential solution be to run InstaDMG on a vanilla 10.5.0 machine with no updates, that way when it checks to see what has to be installed, it sees a machine that needs both of those updates (safari 4 and ilife)

[Patrick Gallagher]

[QUOTE][u]Quote by: spaceout[/u][p]So could a potential solution be to run InstaDMG on a vanilla 10.5.0 machine with no updates, that way when it checks to see what has to be installed, it sees a machine that needs both of those updates (safari 4 and ilife)[/p][/QUOTE]

Or you can delete the /Library/Reciepts/com.apple.pkg.Safari.bom file on your host machine. This gets the install to move on. But this will prevent your host machine from detecting future Safari updates so move the file back when you’re done.

[spaceout]

I am assuming that removing com.apple.pkg.iLifeMediaBrowser_203.bom will allow the ilife update to install as well? What is everyone else doing right now to have a fully updated image (10.5.7, Safari 4.1 and ilife media browser)? It seems as though older revisions of instaDMG have trouble with the 10.5.7 installer and the newer revisions have issues with some of the later System Updates (eg Safari 4).

[Patrick Gallagher]

[QUOTE][u]Quote by: spaceout[/u][p]I am assuming that removing com.apple.pkg.iLifeMediaBrowser_203.bom will allow the ilife update to install as well? What is everyone else doing right now to have a fully updated image (10.5.7, Safari 4.1 and ilife media browser)? It seems as though older revisions of instaDMG have trouble with the 10.5.7 installer and the newer revisions have issues with some of the later System Updates (eg Safari 4).[/p][/QUOTE]

I’m still using 1.4b4 and I haven’t noticed a problem yet with iLifeMediaBrowser. But I did have the Safari4 installer hang up and I remembered seeing your post so I trashed that bom file. I’m using a 10.5.7 disk on this particular image (new 13″ MBP). But my previous image was a 10.5.6 disk with a 10.5.7 delta updater and I didn’t have a problem.

[larkost]

[QUOTE][u]Quote by: spaceout[/u][p]I am assuming that removing com.apple.pkg.iLifeMediaBrowser_203.bom will allow the ilife update to install as well? What is everyone else doing right now to have a fully updated image (10.5.7, Safari 4.1 and ilife media browser)? It seems as though older revisions of instaDMG have trouble with the 10.5.7 installer and the newer revisions have issues with some of the later System Updates (eg Safari 4).[/p][/QUOTE]

The iLife Updater actually looks a the installed versions of the Frameworks directly rather than through package receipts. I really do admire this idea in general, and it is a installer bug that prevents it from working properly (distribution scripts being run outside the chroot jail).

[Author]

Posts