From: William Hubbs <williamh@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] rfc: logrotate and xinetd use flags
Date: Sun, 24 Apr 2011 16:58:23 -0500 [thread overview]
Message-ID: <20110424215823.GA24437@linux1> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
All,
I know a decision about this type of use flag was made in the past, but
especially now with the --newuse option in portage, that decision
bothers me, so I would like to re-open the discussion.
I will use logrotate as my example, but what I'm saying also applies for
xinetd.
I feel that the current approach (using INSTALL_MASK) to control whether
these configuration files are installed or not is not well documented.
We tell people about it on the mailing lists, but I do not know of a
place where it is documented.
Also, it seems to be an all or nothing arrangement. If I do not want
logrotate support, I have to set the INSTALL_MASK then if I decide later
I want it, I have to unset the INSTALL_MASK and run "emerge -e world" to
get the files installed.
If we use a "logrotate" or "xinetd" use flag, it gives the users better
control of which packages have this support, and the --newuse option in
portage can be used to rebuild only the affected packages.
I guess the argument against the use flag was that packages were being
rebuilt just to install configuration files. I can see how that could be
a pita for big packages. Did anyone ever bring up using pkg_config to
un/install these files based on the use flags?
Comments?
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-04-24 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 21:58 William Hubbs [this message]
2011-04-25 2:23 ` [gentoo-dev] rfc: logrotate and xinetd use flags Jeroen Roovers
2011-04-25 5:09 ` [gentoo-dev] " Duncan
2011-04-25 7:13 ` [gentoo-dev] " Alec Warner
2011-04-25 7:44 ` Michał Górny
2011-04-25 20:57 ` Jeroen Roovers
2011-04-25 21:03 ` Michał Górny
2011-04-25 15:39 ` Michał Górny
2011-04-25 15:39 ` Ciaran McCreesh
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=20110424215823.GA24437@linux1 \
--to=williamh@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