From: Henrik Brix Andersen <brix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] New global USE flag: logrotate
Date: Thu, 28 Apr 2005 10:30:03 +0200 [thread overview]
Message-ID: <1114677003.14869.14.camel@sponge.fungus> (raw)
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Hi,
I'd like to propose a new global USE flag named 'logrotate' to add
support for app-admin/logrotate (by installing logrotate config files
to /etc/logrotate.d/).
There are currently one local USE flag named logrotate in
net-proxy/squid, which of course isn't enough to justify having a global
USE flag - but it seems other packages, at least app-admin/syslog-ng,
currently unconditionally install a config file to /etc/logrotate.d/.
There are 4 open enhancement requests in Gentoo bugzilla about ebuilds
which could install such a config file, and I am sure many other ebuilds
could as well (anything that logs to a file).
If there are no objections to this I will make 'logrotate' a global USE
flag once I add a logrotate config file to sys-power/acpid.
Sincerely,
Brix
--
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-04-28 8:30 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 8:30 Henrik Brix Andersen [this message]
2005-04-28 8:51 ` [gentoo-dev] New global USE flag: logrotate 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
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 9:22 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
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
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=1114677003.14869.14.camel@sponge.fungus \
--to=brix@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