The classical build technique of:

Public release is OS x.y.z-1
Machine comes with OS x.y.z
New public release of OS x.y.z+1 supports all previous machines, including the above machine

Still applies here. You should only need to build a single image to support your hardware (glaring exceptions are Santa Rosa MacBook Pros and Aluminum iMacs, both under Tiger. Apple probably never intended those machines to run Tiger, so they became one-offs:

[url]http://docs.info.apple.com/article.html?artnum=306051[/url]

). We are using the same Tiger PPC image for 500MHz TiBooks through Quad-Core G5s.

Regarding which updates to apply, I can’t think of a better way to determine the required updates besides installing a plain vanilla installation and running Software Update until there aren’t any more updates available, noting each update along the way. When moving our InstaDMG installation from 10.5.1 to 10.5.2, I gained a few updates and lost a few (Security Updates rolled into 10.5.2).

– Patrick

> The SRMBP complicates my Tiger imaging strategy but that will be temporary.

Avoid installing this update (IIRC):

[url]http://www.apple.com/support/downloads/macbookprosoftwareupdate12.html[/url]

in your Intel Tiger build and you should be golden for the SR MacBook Pros and backward compatibility. I don’t know what pieces to avoid for an Aluminum iMac, since I’ve not had to build a standard image for those, or even if it’s possible to build an Aluminum iMac Tiger build that is backwards compatible.

If you want the MacBook Pro Software Update 1.2 installed, place the pkg in an appropriate post-restore installation (NetRestore would use the “Post-actions” folder). If it can be installed on the machine being restored, it will, otherwise installer will just fail that package because the machine doesn’t meet the requirements.

– Patrick

Not sure if you noticed this, but you need to have Leading Zeros for your directory structure, or 10 gets run before 2. I.e:

01
02
03
….
10
11
12

The default ls sorting order goes like this
1
10
11
12
2
3
4
5

I ran into that when applying iLife updates BEFORE I installed the Main iLife Package. Needless to say that didn’t quite work.

Maybe the update is subject to the same restrictions as some of Apple’s other updates (QuickTime). Does the install work from the CLI with the following:

[code]#!/bin/bash

export COMMAND_LINE_INSTALL=1
export CM_BUILD=CM_BUILD

/usr/sbin/installer -verbose -pkg /path/to/mbp_su_1.2.pkg -target /path/to_destination_volume[/code]

Otherwise repackaging might be the way to go. Make sure to include whatever restrictions Apple has in place regarding hardware requirements.

– Patrick

[QUOTE][u]Quote by: patgmac[/u][p][QUOTE][u]Quote by: pteeter[/u][p]

Here’s another thing to ponder…

Do people consider Apple software like iWork or iLife candidates for the AppleUpdates InstaDMG folder or the CustomPKG folder?

[/p][/QUOTE]

They would probably be custompkg. iLife wants to only install on the boot volume, so that may need to be repackaged.[/p][/QUOTE]

Don’t the AppleUpdates run before the custom pacakges? If that is the case, then should iLife be installed before the iLife updates? Does that mean iLife should be in the AppleUpdates folder before the updates? Or put the updates in the CustomPKG folder after iLife?

I put anything from Apple in the Apple Updates folder. The first one used to be iLife and the second one was iWork. I’ve changed my setup recently to install iLife from the second grey install disk. But I didn’t have any trouble when it was folder 01 in the Apple Updates folder.

I would then boot from the InstaDMG disk I had made and run Software Update. I’d made note of the order that the updates installed in using Console–>Software Update and Console–>Installer. Then I recreated the order in my Apple Updates folder. I ended up with about 25 updates in that folder but the image always booted and didn’t need updating!

There was a gotcha with iLife. There is a post here about fixing the iLife Support updater
<https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=20102&highlight=iLifeMediaBrowser>

When 10.5.3 comes out I will repeat the whole process.