From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] On the use of bash-completion use flag
Date: Tue, 21 Jun 2011 16:05:59 +0200 [thread overview]
Message-ID: <19968.42311.544289.442891@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <BANLkTik9tW-LrMEt7aSh-t1CvT_wz7TptA@mail.gmail.com>
>>>>> On Tue, 21 Jun 2011, Nguyen Thai Ngoc Duy wrote:
>> --- Comment #2 from Gilles Dartiguelongue <eva@gentoo.org> 2011-06-21 09:35:59 UTC ---
>> Afaik, the bash-completion eclass adds the use flag only to make
>> sure the user has bash-completion and eselect packages installed.
>> This is imho overkill and it indeed meets the point that was made
>> on the ml that installing one file that doesn't in itself depends
>> on anything doesn't warrant a USE flag. Maybe the discussion should
>> be brought to dev ML to make the situation clearer for
>> bash-completion too.
> OK let's hear from the ML. Another good thing from bash-completion
> eclass is that it advertises bash-completion in pkg_postinst (though
> some packages miss this). If we're OK for dev-libs/glib not to use
> bash-completion use flag, what about the others, drop the use flag?
With the flag, some additional files are installed _and_ additional
dependencies like app-shells/bash-completion (which will pull in
further dependencies) are required. Looks like a perfect case for a
USE flag to me. For example, users of embedded systems may not want to
install such additional packages.
Ulrich
next prev parent reply other threads:[~2011-06-21 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 12:20 [gentoo-dev] On the use of bash-completion use flag (Was: [Bug 372031] dev-libs/glib-2.28.* add bash-completion use flag) Nguyen Thai Ngoc Duy
2011-06-21 14:05 ` Ulrich Mueller [this message]
2011-06-23 8:41 ` [gentoo-dev] On the use of bash-completion use flag Gilles Dartiguelongue
2011-06-24 7:07 ` Michał Górny
2011-06-24 7:26 ` "Paweł Hajdan, Jr."
2011-06-24 10:37 ` Ulrich Mueller
2011-07-08 9:12 ` Gilles Dartiguelongue
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=19968.42311.544289.442891@a1i15.kph.uni-mainz.de \
--to=ulm@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