public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Ulrich Mueller <ulm@gentoo.org>
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] use.desc: Correct/clarify SSL/TLS-related flags
Date: Wed, 31 Jan 2018 00:39:24 +0100	[thread overview]
Message-ID: <2735c531-9977-a604-0438-7d0c16437e97@gentoo.org> (raw)
In-Reply-To: <23152.65107.266869.334200@a1i15.kph.uni-mainz.de>


[-- Attachment #1.1: Type: text/plain, Size: 1468 bytes --]

On 01/31/2018 12:22 AM, Ulrich Mueller wrote:
>>  gnome-keyring - Enable support for storing passwords via gnome-keyring
>>  gnuplot - Enable support for gnuplot (data and function plotting)
>> -gnutls - Add support for net-libs/gnutls (TLS 1.0 and SSL 3.0 support)
>> +gnutls - Prefer net-libs/gnutls as SSL/TLS provider (requires USE=ssl if present)
> NACK. This seems to imply that USE="-ssl gnutls" is not a valid
> configuration? What if the user prefers gnutls and therefore has
> globally enabled the gnutls flag, but -ssl for a single package?
> 
> How about "(needs USE=ssl to take effect)" instead?
> 

as I understand it ssl is intended as a generic use flag, of which
gnutls can be one of the providers. In the case of of app-crypt/gnupg
there are only two possible providers, gnutls, and ntbtls, of which only
one is available in tree, so gnutls is the only one, so the only one
relevant for Gentoo is gnutls, hence no use flag for it, either TLS is
enabled, or it is not.

in this scenario I don't see why "ssl -gnutls" would not be a valid
configuration as long as ssl is a generic use flag as it is presented to
be. It doesn't mean never install gnutls, but just not preferring it in
cases where there are other providers of ssl/tls, that the global
description already indicate.

-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-01-30 23:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 22:11 [gentoo-dev] [PATCH] use.desc: Correct/clarify SSL/TLS-related flags Michał Górny
2018-01-30 22:24 ` Kristian Fiskerstrand
2018-01-30 23:22 ` Ulrich Mueller
2018-01-30 23:39   ` Kristian Fiskerstrand [this message]
2018-01-30 23:42   ` Gordon Pettey
2018-01-31  9:53     ` Ulrich Mueller
2018-01-31 13:16     ` nado
2018-01-31 14:49 ` [gentoo-dev] [PATCH v2] " Michał Górny

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=2735c531-9977-a604-0438-7d0c16437e97@gentoo.org \
    --to=k_f@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    --cc=ulm@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