public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: hasufell <hasufell@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: ssl vs openssl vs libressl vs gnutls USE flag foo
Date: Wed, 28 Oct 2015 12:30:34 +0100	[thread overview]
Message-ID: <5630B1DA.3070705@gentoo.org> (raw)
In-Reply-To: <5630B019.5070805@gentoo.org>

On 10/28/2015 12:23 PM, Anthony G. Basile wrote:
> 
> A properly designed sub-USE flag would be useful here and clearly better
> than our REQUIRED_USE.  I think REQUIRED_USE is fine for heterogeneous
> cases, but not when you have something like curl where you can either
> turn ssl on or off.  If it is off, nothing more needs to be specified,
> if it is on, then you must further specify one and exactly one ssl
> provider.
> 

Uhm, curl makes use of REQUIRED_USE heavily, otherwise the use_expand
would not work:
> REQUIRED_USE="
> 	curl_ssl_winssl? ( elibc_Winnt )
> 	threads? ( !adns )
> 	ssl? (
> 		^^ (
> 			curl_ssl_axtls
> 			curl_ssl_gnutls
> 			curl_ssl_libressl
> 			curl_ssl_openssl
> 			curl_ssl_nss
> 			curl_ssl_polarssl
> 			curl_ssl_winssl
> 		)
> 	)"

With the providers syntax from exherbo, this monster would basically be
gone.


  reply	other threads:[~2015-10-28 11:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  2:06 [gentoo-dev] ssl vs openssl vs libressl vs gnutls USE flag foo hasufell
2015-10-28  2:46 ` Rich Freeman
2015-10-28  4:35   ` Gordon Pettey
2015-10-28  6:23   ` [gentoo-dev] " Ryan Hill
2015-10-28 11:16     ` hasufell
2015-10-28 11:23       ` Anthony G. Basile
2015-10-28 11:30         ` hasufell [this message]
2015-10-28 15:11           ` Anthony G. Basile
2015-10-28 11:32         ` Kristian Fiskerstrand
2015-10-28 13:51       ` Rich Freeman
2015-10-28 11:20     ` Kristian Fiskerstrand
2015-10-28 11:24       ` hasufell
2015-10-30 17:55   ` [gentoo-dev] " Michał Górny
2015-10-30 19:35     ` hasufell
2015-10-30 21:16       ` Anthony G. Basile
2015-10-30 22:25         ` Rich Freeman
2015-10-30 23:10           ` Michał Górny
2015-10-30 22:40         ` hasufell
2015-10-30 22:56           ` Michał Górny
2015-10-30 23:13             ` hasufell
2015-10-30 23:06           ` Luis Ressel
2015-10-30 20:07     ` Rich Freeman
2015-10-28  8:36 ` Alexis Ballier
2015-10-28 11:21   ` hasufell
2015-10-29 13:27 ` Chí-Thanh Christopher Nguyễn

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=5630B1DA.3070705@gentoo.org \
    --to=hasufell@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