public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: williamh@gentoo.org
Subject: Re: [gentoo-dev] rfc: logrotate and xinetd use flags
Date: Mon, 25 Apr 2011 09:44:24 +0200	[thread overview]
Message-ID: <20110425094424.5de5717d@pomiocik.lan> (raw)
In-Reply-To: <20110424215823.GA24437@linux1>

[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]

On Sun, 24 Apr 2011 16:58:23 -0500
William Hubbs <williamh@gentoo.org> wrote:

> 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.

I'm currently working on improving the situation. I'd like to create
a tool which would allow users to easily add and remove INSTALL_MASKs
(including a few common sets), and rebuild the packages as necessary.
This, however, would require some fixes in portage [1].

> 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?

I don't think that would work. And if it does, then either PM or even
PMS is broken by design. The pkg_config() phase should have the same
flags set as the build had, or don't refer to flags at all.

In addition, upstream-installed config files often require running sed.
And this requires unpacking & configuring the package. Really don't
seem appropriate for pkg_config().

[1] http://bugs.gentoo.org/show_bug.cgi?id=364633

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2011-04-25  7:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24 21:58 [gentoo-dev] rfc: logrotate and xinetd use flags William Hubbs
2011-04-25  2:23 ` 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 [this message]
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=20110425094424.5de5717d@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=williamh@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