Date: Mon, 17 May 2004 11:32:36 +0200 From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de> To: Oliver Eikemeier <eikemeier@fillmore-labs.com> Cc: Lars.Koeller@Uni-Bielefeld.DE Subject: Re: ports overwriting configuration files Message-ID: <m3u0yfbdqj.fsf@merlin.emma.line.org> In-Reply-To: <40A682F2.1050905@fillmore-labs.com> (Oliver Eikemeier's message of "Sat, 15 May 2004 22:52:02 %2B0200") References: <7DEC7598-A53D-11D8-AFB0-0003937C4014@knowledgetap.com> <20040514011513.GA51312@wombat.localnet> <20040515180408.GA97698@numachi.com> <40A682F2.1050905@fillmore-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Oliver Eikemeier <eikemeier@fillmore-labs.com> writes: > Grmbl. It is hard to think of an algorithm that recognizes `real' configuration > files automatically. In my ports I install *.default configuration files, which > *are* overwritten with new ones. The `real' configuration files are not touched > if they are different (edited) from the default ones, but of course I know which > are the real and which are the default files. Well, the ports I maintain - if they include configuration - will run cmp(1) to check if the configuration file is the same as the example file (however it is named, *.dist, *.sample, ...) and only if it is the same, will be removed. For some ports that have a linear collection of independent options, Sam Varshavchik's sysconftool (used, for instance, by mail/cone), is the right thing to use, but this will not work for nested configurations and configurations with sections that can be repeated, think Samba. -- Matthias Andree Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m3u0yfbdqj.fsf>