I'll add my vote to Bill's side. I use cfengine to roll out my configuration files and then install software and (re)start services. I found it really annoying that installing postfix overwrote my configuration files. If it does that during an update too it is very bad.
Martin > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bill Campbell > Sent: Friday, June 20, 2003 6:09 PM > To: [EMAIL PROTECTED] > Subject: Re: Suggestions for build standards > > > On Fri, Jun 20, 2003 at 11:23:11PM +0200, Michael van Elst wrote: > >On Fri, Jun 20, 2003, Bill Campbell wrote: > > > >Bill, > > > >> 1. Specify all configuration files that are essential to program > >> operation %config(noreplace)'' (e.g. postfix's > main.cf, samba's > >> smb.conf, etc.) to avoid breaking production systems > when doing > >> updates. > > > >I don't think there is a correct way. You may either fail > with the old > >or the new configuration. With the default %config the user > >configuration is only modified when the default > configuration changes, > >in that case it is likely that the user configuration is broken. > > I'm most concerned with programs like postfix which require > extensive localization, and killing the MTA at an ISP is a > major PITA (but I probably don't have to tell the C&W guys > that :-). Our postfix/Makefiles are extensively modified to > automatically incorporate alias files from mailing lists, > update the virtual file from multiple domain files, etc., and > it can take a while to get these back in order after an > update. Weitze makes a point of backwards compatibility with > postfix so there's not much chance of buggering it entirely > by staying with the local modifications. > ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
