-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 heya,
On Tuesday 31 January 2006 12:31, Ciaran McCreesh wrote: > See, you're not really taking into account the cost of sticking files > in /etc. For packages where an etc entry is low cost, it's already > done. What is the "cost" you are referring to specifically? I think I know but I'd like a specific definition. > For things like bash completion and log rotation, the cost of > installing a file into /etc can be extremely high, so it shouldn't be > forced upon system administrators unless they ask for it. The same goes > for cron entries for packages where the cron part isn't a core > operation. Agreed, the question then though is how to manage it. Is USE the right way? Given that there will always be a couple of exceptions, is it not reasonable to expect that all packages that install cron entries do it in a consistant manner? (and for a moment can certain peoples fear of breaking existing installations be put aside, we are paralysed if we let fear govern what we will consider, if we did decide on something that might ostensibly break existing installations or cause "needless" recompiles we can address those concerns via work around means if necessary once a standard has been decided on). > What would be nice is a ban on .example files in anywhere covered by > CONFIG_PROTECT. We have /usr/share/doc/ for those. Agreed. Personally I think example files belong in /usr/share/doc, but I also think that config files should be written out to the correct dirs and external tools like etc-update/dispatch-conf be used to manage them. - -- Benjamin Smee (strerror) crypto/forensics/netmail/netmon -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.9.20 (GNU/Linux) iD8DBQFD3248AEpm7USL54wRAovuAJ40BsTPlabOLD2ODppilSdOdjQ/sgCeK40o 9PK6bmUlFY72fEBoKnTSGx8= =5ibW -----END PGP SIGNATURE----- -- [email protected] mailing list
