public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Hjalmarsson <xake@rymdraket.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] when to use a function and an implementation use flag.
Date: Wed, 24 Mar 2010 19:30:54 +0100	[thread overview]
Message-ID: <1269455454.31227.12.camel@lillen> (raw)

I took a look at qemu-kvm and found something I percieve as funny:
It had a gnutls use-flag, but no ssl useflag.

As I see it is I want ssl/tls support it should be sufficient to enable
USE="ssl" and let the maintainer of said ebuild decide which
implementation (if more then one) I am better off with and only care
about the USE="gnutls openssl nss" if i really think the maintainer is
wrong.

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.

When I wrote a bug about this I got a rather short reply from maintainer
about pointing me to the policy about this.
Now I know there was a disscussion a while back about this on the
mailinglist, but google fails me to find it, looking into the Gentoo
Development Guide [1] it fails me too.

There is not a _single_ word about how to handle if there is only one
implementation, but two use flags for this (one for the function
provided - ssl - and one for the actual implementation - gnutls).

So I have a question:
Is there no policy about this?
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




             reply	other threads:[~2010-03-24 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 18:30 Peter Hjalmarsson [this message]
2010-03-27 14:44 ` [gentoo-dev] when to use a function and an implementation use flag Petteri Räty
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=1269455454.31227.12.camel@lillen \
    --to=xake@rymdraket.net \
    --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