public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] when to use a function and an implementation use flag.
Date: Sat, 27 Mar 2010 16:44:46 +0200	[thread overview]
Message-ID: <4BAE19DE.70206@gentoo.org> (raw)
In-Reply-To: <1269455454.31227.12.camel@lillen>

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

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?

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

USE="ssl" --> should always give you ssl support

> If there is could someone please point me towards it and also it in that
> case may be time to update the gentoo development guide.
> 
> [1]
> http://devmanual.gentoo.org/general-concepts/use-flags/index.html#conflicting-use-flags
> 

If you read the example code you see what I said is already done in the
example code.

Opened a bug for qemu-kvm:
http://bugs.gentoo.org/show_bug.cgi?id=311627

Opened a bug for repoman:
http://bugs.gentoo.org/show_bug.cgi?id=311629

Regards,
Petteri



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2010-03-27 14:44 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 [this message]
2010-03-28  6:06   ` Doug Goldstein
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=4BAE19DE.70206@gentoo.org \
    --to=betelgeuse@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