From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Default Ebuild behaviour
Date: Tue, 31 Jan 2006 12:31:58 +0000 [thread overview]
Message-ID: <20060131123158.276847a4@snowdrop.home> (raw)
In-Reply-To: <200601311211.59355.strerror@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
On Tue, 31 Jan 2006 12:11:49 +0000 "Benjamin Smee (strerror)"
<strerror@gentoo.org> wrote:
| While I understand various developers concerns about cluttering /etc
| (especially embedded), I don't see why this should stop the policy of
| writting ebuilds that work and have expected tools around them.
| Precisely what that constitutes is the real question.
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. 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.
What would be nice is a ban on .example files in anywhere covered by
CONFIG_PROTECT. We have /usr/share/doc/ for those.
--
Ciaran McCreesh : Gentoo Developer (King of all Londinium)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-31 12:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 12:11 [gentoo-dev] Default Ebuild behaviour Benjamin Smee (strerror)
2006-01-31 12:31 ` Ciaran McCreesh [this message]
2006-01-31 14:03 ` Benjamin Smee (strerror)
2006-01-31 15:47 ` Ciaran McCreesh
2006-01-31 17:06 ` Benjamin Smee (strerror)
2006-01-31 17:24 ` Ciaran McCreesh
2006-01-31 20:15 ` Donnie Berkholz
2006-01-31 22:43 ` Henrik Brix Andersen
2006-01-31 22:53 ` Ciaran McCreesh
2006-01-31 23:03 ` Henrik Brix Andersen
2006-01-31 23:17 ` Ciaran McCreesh
2006-02-01 0:02 ` Henrik Brix Andersen
2006-01-31 23:14 ` Francesco Riosa
2006-02-01 1:32 ` Georgi Georgiev
2006-02-01 10:56 ` Rob Holland
2006-02-01 10:41 ` Benjamin Smee (strerror)
2006-01-31 19:51 ` Chris Gianelloni
2006-01-31 20:22 ` Alin Nastac
2006-02-01 8:59 ` Andreas Vinsander
2006-02-01 9:05 ` Andreas Vinsander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060131123158.276847a4@snowdrop.home \
--to=ciaranm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox