[larkost]

Thanks! And everything is now go for the trip to Sweden, so come up and introduce yourself before or after the presentation.

[larkost]

If you are using InstaUp2Date, then you can’t put anything of your own into CustomPKG or BaseUpdates. You have (at least) the iLife ’08 installer in there, and it is telling you that it will not erase it (since it is not an empty folder or a symlink).

[larkost]

The chroot system was not put in until rev196, so rev179 should have this problem.

I would recommend using HEAD (rev210 was the last change to the trunk, later ones at the moment have only been for the development of version 2). To do this remove the ‘-r number’ from the command.

[larkost]

Unfortunately at least the iLife update is written really well, it actually checks the versions on the two frameworks that it updates, and I wouldn’t want to go messing with this. The only problem is that it is escaping the chroot jail, and that is something that has to be solved by the installer team. I have a bug filed, but others should also file this with impact statements to get Apple to value it.

[larkost]

As other people have said, a clean build is the whole point of InstaDMG.

That being the case, one of my goals for 2.0 is to have checkpoints along the way. Every checkpoint would cost quite a bit of disk space (it would be all of the differences between that point and the base install), but it would be a safe way of starting the process at a known point. Of course if you changed anything before the checkpoint it could not be used.

And I really want to get back to work on 2.0… and it is now next on my list of things. Right now I want to finish a little bit of C work I have, and then there is the job search (my fingers are crossed for the big interview tomorrow)… and then a few other little projects that have to be continued… *sigh* Not having a job is too much work!

[larkost]

Assuming you are using a relatively recent version of InstaDMG, then it is in InstaDMG/AddOns/createUser.

[larkost]

Why not use the one that comes with InstaDMG? That one already has all of this figured out for you.

[larkost]

InstaUp2Date wants to control everything in the folders. It will not allow anything in there beforehand. I am perfectly happy if someone writes a patch to change this, but it then has to deal with making sure that things are not duplicated (I don’t see that happening), and remain in the right order.

Far easier would be to just to follow the way InstaUp2Date wants things, and let it control those folders completely.

[larkost]

Newer computers will automatically set verbose startup mode when the startup disk set in EFI is not available (and it has to search for the next valid one). Since you wiped away the volume that used to be the startup volume (or more specifically: wiped away the volume UUID) it falls into this mode. The solution is to go into the startup disk control panel and set your startup volume. If you have an imaging system, you just need to make sure that it sets the startup volume before rebooting into the new image.

[larkost]

You can pretty much bet that I am always running the latest development version of InstaDMG… or rather that the latest development version of InstaDMG is what I am running… *grin*. But I have seen 10.5.7 success with rev200 and above (so with chroot jails). Note that Mail.app was masked out on my image (it was not really usable with the quotas on network homes), so I don’t know that one specifically, but 200 did correct a bunch of things like that.

[larkost]

I made successful images with 10.5.7 (running form 10.5.7), but I know that iLifeSupport is a problem (and my guess is Safari 4 has the same problem), and have written about it a few times, and the two possible corrections:

1. You might be able to use an InstallerChoices.xml (new style) to get around the problem (I have not had the time to test).

2. I have registered basic bugs with Apple on this, and intend to file much better ones once I get some extra time (create some examples to show the bugs without requiring the big packages).

On a side note, I just lost my job in a large layoff, so I am having to spend more time looking for a new job than working on InstaDMG. I plan get back to it, but it will be a few weeks at least.

[larkost]

It looks like your base image is read/write. The second line in your log is it failing to checksum the base image (and then not mounting it). At this point the image must be read-only (a safety precaution). You did find a bug in that the process should have stopped cold at that point. I have just checked in a bug-fix for that (rev210).

[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).

[larkost]

My understanding is that MacOS X in general does not support Kerberos for authentication to proxys. So you are probably not going to get this to work for Safari. But I think you can get this to work with Firefox. I have never actually done this, as I have never worked with a proxy that needed authentication.

Note that all of this is with 10.5. I have no idea about 10.6. But if this is important to you make sure to file a radar request for it: http://bugreport.apple.com. Make sure to provide impact statements with your report (how badly does it affect how many users, and how does this keep you from buying Apple products).

[larkost]

There is some good documentation at:

[url]http://s.sudre.free.fr/Stuff/PackageMaker_Howto.html[/url]

[Author]

Posts