From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] when to use a function and an implementation use flag.
Date: Sun, 28 Mar 2010 01:06:41 -0500 [thread overview]
Message-ID: <eafa4c131003272306p201abbabq7c08457c49103a1d@mail.gmail.com> (raw)
In-Reply-To: <4BAE19DE.70206@gentoo.org>
On Sat, Mar 27, 2010 at 9:44 AM, Petteri Räty <betelgeuse@gentoo.org> wrote:
> On 03/24/2010 08:30 PM, Peter Hjalmarsson wrote:
>
>> For qemu-kvm the problem is that there is only one implementation (i.e.
>> gnutls), and if I want to have ssl support I have to enable gnutls for
>> this package.
>
> In this case the ebuild should have only ssl use flag.
>
>> When I wrote a bug about this I got a rather short reply from maintainer
>> about pointing me to the policy about this.
>
> Where did he point you to?
I didn't point him anywhere. I merely asked him for a policy on this.
Because senseless changes in USE flags will require my 9 VM servers
will need to be tweaked around for a pointless USE flag change and I
don't need administrative burden for the sake of administrative
burden.
>
>> So I have a question:
>> Is there no policy about this?
>
> The policy is that USE="ssl" controls whether to enable ssl support in
> general. Then the specific use flags like gnutls and openssl control
> what implementation to use if the package supports multiple.
Again, this policy is stated but no one can point me to anything. The
closest thing to a "policy" is you sending a follow up e-mail to the
dev list to make this a policy.
--
Doug Goldstein
next prev parent reply other threads:[~2010-03-28 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 18:30 [gentoo-dev] when to use a function and an implementation use flag Peter Hjalmarsson
2010-03-27 14:44 ` Petteri Räty
2010-03-28 6:06 ` Doug Goldstein [this message]
2010-03-28 17:21 ` Alec Warner
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=eafa4c131003272306p201abbabq7c08457c49103a1d@mail.gmail.com \
--to=cardoe@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