--- Juergen Daubert <jue@jue.li> wrote:
Sorry, but I guess, that you everything-into-/etc guys read over one important point of Nick's mail:
<quote> Also, /etc is usually protected because that is /etc/pkgadd.conf's default. /usr/etc is usually overwritten with each release, which insures that the upgrade works out of the box. Isn't the latter preferable to the support nightmare of persistent configuration files which might be incompatible in some way with the upgraded API? </quote>
That's at least important for progs like gtk, sane, mutt, nail etc., the settings are important for the applications, but the user shouldn't ever touch them and they _must_ be overwritten with new releases.
kind regards Juergen
I agree. While I expressed distress with xdg/gnome-menus problems, I do not feel that /etc is the proper place for all package configurations. In fact, I'd like to see more ports make use of /usr/etc, as things like gdm, cups, and ssh end up requiring lots of rejmerg attention. /etc should be reserved for very essential, and rather static, system config files. *If* a user ends up having to edit something in /usr/etc, he/she should know well enough to make an addition for it in /etc/pkgadd.conf if he/she so desires. Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs