Hi all
I encourage those interested in this is issue to read the following August 04 2006 macworld article:
Repairing permissions: What you need to know
What repairing permissions does and whether you should do it
By Dan Frakes
http://www.macworld.com/2006/08/secrets/repairpermissions/index2.php
It's a rather in depth look at the question and I thought I would post it here since there seems to be a lot of heated debate here in the rink concerning this matter.
I will also present a snippet related to the context at hand. It answers the question of whether repairing before and/or after updates is worthwhile and why it is or is not worthwhile.
"Do I need to repair permissions before installing an update to Mac OS X?
In a word, no. When you install a Mac OS X update, you’re required to authenticate—provide an admin-level username and password—in order for the installation to proceed. When you authenticate, you’re allowing the installer to run with the equivalent of root access. What this means is that the installer is not constrained by Mac OS X’s permissions system—it ignores the normal restrictions of file and folder permissions. This is necessary for Installer to be able to update Mac OS X, but, more important for the current discussion, it also means that “incorrect” permissions shouldn’t cause problems with the installation.
The only real benefit to repairing permissions before a Mac OS X update is that if you do so, then immediately install the update, and then repair permissions again immediately afterwards, you can be pretty confident that any permissions issues that are found are a result of the update. But at that point you’ve also fixed the problem(s), so the pre-install “repair” provided you with little more than academic knowledge."
This, from the article may also be of interest.
"Given that Apple recommends repairing permissions after updating Mac OS X, why doesn’t Apple’s Installer do it automatically?
I asked Apple that very question; the company declined to comment. For what it’s worth, repairing permissions isn’t the only procedure to fall into this category; there are many other useful procedures and processes Mac OS X doesn’t automatically perform. For example, it’s a good idea to periodically check your hard drive for problems, and Apple recommends doing so; although Mac OS X could easily perform this task on a weekly basis, it doesn’t."
Personally I haven't read the article in full yet but I think we all should be informed considering the circumstance and folks, I know these debates get heated and we all like to take the trophy home but let's be nice to one another. We are all in the same boat.
Anyway, I hope this helps and again, I encourage people who are interested to at least skim the article.
INMHO it looks more and more like this is an issue Apple will have to contend with in some form or other.