Juergen Daubert wrote:
On Tue, May 10, 2005 at 06:41:38PM -0400, Victor wrote:
Matt Housh wrote:
Greetings, all.
I'd like to start some discussion about explicitly setting sysconfdir (or confdir or whatever the package uses) back to /etc instead of letting the default prefix decide it. I'd love to hear what everyone thinks of this because it's causing me and jdolan at least a few issues.
I think "everything in /etc" is better, as long as offenders with lots of configs go into /etc/<package>/* like what samba, apache, etc do.
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.
can't this be solved by adding logic into pkgadd.conf that has a NOT clause in it and just add NOT <gtk.config> that will allow those NOT things to be overwritten? Or just remove /etc from the list and specify everything that should NOT be automatically updated. There is no way to cleanly handle this and /usr/etc doesn't solve the problem, it just moves it to another location. Victor