From: Alec Joseph Warner <warnera6@egr.msu.edu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New global USE flag: logrotate
Date: Tue, 02 Aug 2005 13:48:17 -0400 [thread overview]
Message-ID: <42EFB1E1.6080208@egr.msu.edu> (raw)
In-Reply-To: <20050802183330.07d9a458@snowdrop.home>
Ciaran McCreesh wrote:
> On Tue, 02 Aug 2005 09:48:25 -0700 Donnie Berkholz
> <spyderous@gentoo.org> wrote:
> | Tom Martin wrote:
> | | Hi list,
> | |
> | | Bug 97447 wants a logrotate USE flag, which is used by about five
> | | packages locally. Unless there are any objections, I'll globalify it
> | | later today.
> |
> | I think this flag is a bad idea. Why should I have to recompile a
> | package to get some files that go in /etc? Either install them
> | unconditionally or don't install them at all.
>
> Files in /etc are expensive in terms of sysadmin time. The only things
> in /etc should be things that are both necessary and likely to be
> modified by a sysadmin.
>
And who makes that call, shouldn't the sysadmin decide what is necessary
in /etc and what is not? Why shouldn't portage just install stuff in
/etc and let the sysadmin figure out what needs to be there via
INSTALL_MASK?
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-02 17:52 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 9:22 [gentoo-dev] New global USE flag: logrotate Tom Martin
2005-08-02 10:44 ` Anthony Gorecki
2005-08-02 12:17 ` Chris Gianelloni
2005-08-02 17:04 ` Tom Martin
2005-08-02 17:24 ` Chris Gianelloni
2005-08-02 12:34 ` tomk
2005-08-02 16:48 ` Donnie Berkholz
2005-08-02 17:01 ` Alec Warner
2005-08-02 17:33 ` Ciaran McCreesh
2005-08-02 17:48 ` Alec Joseph Warner [this message]
2005-08-02 17:59 ` Ciaran McCreesh
2005-08-02 17:52 ` Donnie Berkholz
2005-08-02 18:12 ` Ciaran McCreesh
2005-08-02 17:58 ` Alin Nastac
2005-08-03 23:50 ` Tom Martin
-- strict thread matches above, loose matches on Subject: below --
2005-04-28 8:30 Henrik Brix Andersen
2005-04-28 8:51 ` Robin H. Johnson
2005-04-28 10:34 ` Henrik Brix Andersen
2005-04-28 10:44 ` Robin H. Johnson
2005-04-28 11:01 ` Thomas de Grenier de Latour
2005-04-28 11:01 ` Henrik Brix Andersen
2005-04-28 14:00 ` Mike Frysinger
2005-04-28 14:08 ` Thomas de Grenier de Latour
2005-04-28 12:05 ` Ciaran McCreesh
2005-04-28 12:56 ` Georgi Georgiev
2005-04-28 13:41 ` Cory Visi
2005-04-28 13:44 ` Lance Albertson
2005-04-28 13:47 ` Ciaran McCreesh
2005-04-28 15:23 ` Chris Gianelloni
2005-04-28 15:51 ` Thomas de Grenier de Latour
2005-04-28 19:48 ` Donnie Berkholz
2005-04-28 20:16 ` Ciaran McCreesh
2005-04-28 20:21 ` Donnie Berkholz
2005-04-28 22:18 ` Grant Goodyear
2005-04-28 22:28 ` Donnie Berkholz
2005-04-29 0:36 ` Jason Stubbs
2005-04-29 0:43 ` Donnie Berkholz
2005-04-29 12:26 ` Chris Gianelloni
2005-04-29 13:25 ` Dan Meltzer
2005-04-29 13:55 ` Jason Stubbs
2005-04-29 15:52 ` Chris Gianelloni
2005-04-29 16:17 ` Jason Stubbs
2005-04-29 17:26 ` Chris Gianelloni
2005-04-29 17:25 ` Jason Stubbs
2005-04-29 17:46 ` Chris Gianelloni
2005-04-29 18:03 ` Jason Stubbs
2005-04-29 15:32 ` Chris Gianelloni
2005-04-29 17:44 ` Robin H. Johnson
2005-04-29 18:06 ` Jason Stubbs
2005-04-29 18:59 ` Chris Gianelloni
2005-04-29 19:17 ` Donnie Berkholz
2005-04-29 9:32 ` Christian Birchinger
2005-04-28 22:32 ` Tom Wesley
2005-04-28 23:10 ` Spider
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=42EFB1E1.6080208@egr.msu.edu \
--to=warnera6@egr.msu.edu \
--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