On 10/28/15 7:16 AM, hasufell wrote:
On 10/28/2015 07:23 AM, Ryan Hill wrote:
Agreed. If there's one choice then "ssl" should be used. openssl/libressl/etc
should really be considered sub-flags of ssl.
This is what I did with curl. USE=ssl means one and exactly one ssl
provider must be
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/28/2015 12:23 PM, Anthony G. Basile wrote:
> On 10/28/15 7:16 AM, hasufell wrote:
>> On 10/28/2015 07:23 AM, Ryan Hill wrote:
>>> Agreed. If there's one choice then "ssl" should be used.
>>> openssl/libressl/etc should really be considered
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/28/2015 07:23 AM, Ryan Hill wrote:
>
> Agreed. If there's one choice then "ssl" should be used.
> openssl/libressl/etc should really be considered sub-flags of ssl.
>
If we are introducing a new and proper way to define this it might
make
On Wed, Oct 28, 2015 at 7:16 AM, hasufell wrote:
>
> This is outside of the scope of this thread, but there are already
> distros that have fixed this:
> 1. NixOS [0] with truly declarative configuration format, e.g. something
> like:
> packages.ssl.provider = openssl;
Well,
On 10/28/2015 07:23 AM, Ryan Hill wrote:
>
> Agreed. If there's one choice then "ssl" should be used.
> openssl/libressl/etc
> should really be considered sub-flags of ssl.
>
> I really wish we had some way of specifying this to make things clearer to the
> user, so they could see exactly how
On 10/28/2015 12:20 PM, Kristian Fiskerstrand wrote:
> On 10/28/2015 07:23 AM, Ryan Hill wrote:
>
>
>> Agreed. If there's one choice then "ssl" should be used.
>> openssl/libressl/etc should really be considered sub-flags of ssl.
>
>
> If we are introducing a new and proper way to define this
On 10/28/15 7:30 AM, hasufell wrote:
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