Originally Posted by columbus
This is why it would take the time, solving problems like this!
From my interpretation:
 Install 10.6
... sometime in the not too distant future ...
 Install 10.6.1 via software update
... sometime later in the not too distant future ...
 Reinstall 10.6 system automatically figures out which components to alter/ammend/overwrite to get back to step 2.
But what if:
 Install 10.6.2
 Install 10.6.3 ... and oh crap, it's broken one of my applications, I want to go back to 10.6.2
a) Install 10.6 which will automatically leave me at 10.6.3 according to the article
b) Install 10.6 followed by the 10.6.2 combo updater (assuming it's still available)
c) Just install the 10.6.2 combo updater, skipping the 10.6 installer
Originally Posted by melgross
It's really no different from before. This is just for convenience when you're doing the upgrade.
As before, when doing a re-install, you just install the combo update afterwards.
But will the combo updaters act just like the 10.6 installer and automatically leave me at the more recent version (will the 10.6.2 updater put me at 10.6.2 or 10.6.3)? Even if they don't, the 10.6.2 combo updater will have no knowledge of any new files (completely new, not just updates of previous versions of files). So even if the 10.6.2 updater leaves you at 10.6.2, you might have orphaned 10.6.3 files which might cause problem.
Ok, ok, I'm sure Apple has thought this through and have considered the possible scenarios. We are all just curious how they are implementing this feature.
Originally Posted by ecking
I hope that ability can be toggled off during installation, that's horrible for editors. I'm finishing up a job in FCP6 soon and I was thinking of giving fcp7 a try, imagine when I found a problem and wanted to go back to FCP6 my fcp6 disks were automatically giving me fcp7?
We are only talking about OS installs, not application installs. There is no evidence to suggest Apple is doing the same thing for app installers.