The good folks at the Omni Group must be happy. Apple has just promoted their browser to be part of the iLife suite of applications. Well, almost.
Like any good Mac user I today proceeded to download the iLife updates from Software Update. While I am aware of the fact all applications should be closed when applying upgrades, I confess I was at the time tinkering within OmniWeb and didn’t think much of it - especially since all my iLife applications were safely out of the way.
Suddenly, Software Update was seized by a newfound fury: application icons were bouncing and my computer beeping like if it had a life of its own. Indeed, it was desperately trying to get me to see a dialog instructing me to “Quit iWeb before applying this update”.
From the “iWeb” reference, I gathered “this update” referred to the iWeb installer. All is well, of course, except I was most certainly not using iWeb at the time - and I am most certainly not using iWeb at all, anyway. So, why the insistence? With no way to pause the dialog, I was forced to look into a solution.
Of course, the iWeb installer package runs a preflight script that checks whether this application is launched or not and instructs the user to quit it if so. Only this script seems to detect any application containing the word “Web” in its name as iWeb, including good old OmniWeb.
Quitting OmniWeb and validating the dialog indeed caused the script to proceed normally.
I know very little about bash scripting and regular expressions. In fact, I’m better at cooking croque monsieurs and coq au vin than at getting my terminal echo “Hello world” with a script. Yet, it seems to me something like that in an Apple installer is rather unsettling.