At 11:55 AM -0700 4/11/2002, Alex S wrote: > >My real point is not a matter of technical savviness. It's more that >something Apple pushed out broke something I, and others have setup. I >might even have been more cautious about the update IF they listed it as >something being updated, which they did NOT do.
Alex, http://docs.info.apple.com/article.html?artnum=120111 lists only the security-related components in the update. If you are concerned about the complete contents of an update (and I would suggest that in any case where you are in the habit of replacing apple-supplied binaries you do), I recommend that you examine an exhaustive manifest before performing the install. If you can't find a site that publishes a manifest, then learn how to extract one for yourself using lsbom(8) or pax(1) or using a tool like pacifist. In this case, Apple listed mod_ssl 2.8.7 (technically 2.8.7-1.3.23 as mod_ssl is always paired with specific apache versions) as the updated version. This implies that Apache would be updated to 1.3.23. From that, it stands to reason that a number - if not most - of the Apple-delivered DSOs would be recompiled as well and included in the install. A good low-noise site for keeping track of these sort of updates and their implications is Stepwise. Their announcement on the update http://www.stepwise.com/Articles/News/2002-04-05.01.html includes Apache-specific information. They don't provide perl & mod_perl instructions on Stepwise, but if Apple changes something with Apache, they'll flag it and you can notice it there. As others have noted, there is nothing new under the sun. These issues are common to all *nix packaging systems. Those who don't want Apple to break what they've installed should either install things in other locations (fink does this, from what I understand) or leave the Apple- installed packages alone. It's a good lesson to learn. It's unfortunate that it's more frequently learned firsthand than through secondhand annectodal accounts. -Charles [EMAIL PROTECTED]
