On Thu, 22 Oct 2015 18:36:03 -0700
Zac Medico wrote:
> This makes it possible to sync repositories inside $ROOT.
>
> X-Gentoo-Bug: 563836
> X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=563836
> ---
> pym/portage/repository/config.py | 7 ++-
> 1 file
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
On 10/28/2015 09:36 AM, Alexis Ballier wrote:
> On Wed, 28 Oct 2015 03:06:59 +0100
> hasufell wrote:
>> A is not that difficult. Most uses of 'openssl' can just be replaced
>> with 'ssl', others probably with '!gnutls?' even. A few exotic ones
>> might stay and we will have
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sheesh. That expression barely fits in a tweet. ;) Please just use
intermediate statements or an if or something. Otherwise LGTM.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG
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
On Tue, 27 Oct 2015 22:46:35 -0400
Rich Freeman wrote:
> On Tue, Oct 27, 2015 at 10:06 PM, hasufell wrote:
> >
> > B) 1 feature flag, 3 strict provider flags
> > * ssl: enable any sort of SSL/TLS support
> > * gnutls: only to enable gnutls provided ssl
On Wed, 28 Oct 2015 03:06:59 +0100
hasufell wrote:
> A is not that difficult. Most uses of 'openssl' can just be replaced
> with 'ssl', others probably with '!gnutls?' even. A few exotic ones
> might stay and we will have to advice users to set USE="openssl
> libressl"
On 10/28/2015 04:44 AM, Alexander Berntsen wrote:
> Sheesh. That expression barely fits in a tweet. ;) Please just use
> intermediate statements or an if or something. Otherwise LGTM.
I've split it with an if, and also eliminated a redundant comparison
since long(cache_mtime) ==
14 matches
Mail list logo