public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ssl vs openssl vs libressl vs gnutls USE flag foo
Date: Fri, 30 Oct 2015 17:16:02 -0400	[thread overview]
Message-ID: <5633DE12.3020109@gentoo.org> (raw)
In-Reply-To: <5633C686.7070105@gentoo.org>

On 10/30/15 3:35 PM, hasufell wrote:
> On 10/30/2015 06:55 PM, Michał Górny wrote:
>> We have no way of saying 'I prefer polarssl, then gnutls, then
>> libressl, and never openssl'.
> I don't think this is something that can be reasonably supported and it
> sounds awfully automagic. And I don't see how this is possible right
> now, so I'm not really sure what you expect to get worse.
>
> E.g. -gnutls pulling in dev-libs/openssl is not really something you'd
> expect. If we go for provider USE flags, then things become consistent,
> explicit and unambiguous. The only problem is our crappy implementation
> of providers USE flags via REQUIRED_USE.
>
I'm not sure what mgorny has in mind, but the problem I see with saying 
I want just X to be my provider system wide is that some pkgs build with 
X others don't, other pkgs might need a different provider.  So it might 
make sense to order them in terms of preference: X1 > X2 > X3 ... and 
then when emerging a package, the first provider in the preference list 
that works is pulled in for that package.

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA



  reply	other threads:[~2015-10-30 21:16 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
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 [this message]
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=5633DE12.3020109@gentoo.org \
    --to=blueness@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