Apple should take a page from RedHat's book. When redhat replaces key pieces like samba or apache, it leaves the existing configs intact with a ..rpmsave extension. That makes it trivial to put your custom configurations back in place.
As for custom built software, ditto to what Chris and others have said. Put it in /usr/local or use fink to install it somewhere independent of "system" software. Chris wrote: > On Thursday, November 7, 2002, at 09:43 AM, David Wheeler wrote: > > > There's the rub -- I don't think you *can* "prevent future OS updates > > from writing over our custom versions." That's why I choose to simply > > disable Apple's Apache and create a startup bundle for my own. > > Since the updates necessarily run as root, the only way for you to > protect customizations from them is to hide them where Apple will not > be updating! I have had to change several files after upgrades ... > files that handle swapfile on a non-boot partition, for example ... a > nuisance. An "expert mode" in the installer/upgrader would be nice, > letting admins check/uncheck and perhaps preview replacements in /etc > and perhaps elsewhere. > > Your Apache/perl instructions are great, and your sharing your > experience here and in publication is greatly appreciated. > > Best regards, > --Chris
