From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1F3w9T-00070z-QM for garchives@archives.gentoo.org; Tue, 31 Jan 2006 14:06:36 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0VE5dHN023617; Tue, 31 Jan 2006 14:05:39 GMT Received: from phasar.techops.uk.betfair ([213.86.197.188]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0VE3exR023900 for ; Tue, 31 Jan 2006 14:03:40 GMT Received: by phasar.techops.uk.betfair (Postfix, from userid 1000) id 7F4C45ACB; Tue, 31 Jan 2006 14:03:40 +0000 (UTC) From: "Benjamin Smee (strerror)" Organization: Gentoo To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Default Ebuild behaviour Date: Tue, 31 Jan 2006 14:03:38 +0000 User-Agent: KMail/1.9 Cc: Ciaran McCreesh References: <200601311211.59355.strerror@gentoo.org> <20060131123158.276847a4@snowdrop.home> In-Reply-To: <20060131123158.276847a4@snowdrop.home> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601311403.40320.strerror@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Archives-Salt: 81fa0cdb-3187-4354-8e12-18dda537ea32 X-Archives-Hash: 9442d54e7270cc76c33c8f2b421a3587 -----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----- -- gentoo-dev@gentoo.org mailing list