From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] use.desc: Correct/clarify SSL/TLS-related flags
Date: Wed, 31 Jan 2018 10:53:34 +0100 [thread overview]
Message-ID: <23153.37406.445528.171039@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <CAHY5MeeDpAB6oMH-9CczG-xtnFgYPzd+XVHTqA4uB4fOFNQeCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
>>>>> On Tue, 30 Jan 2018, Gordon Pettey wrote:
> On Tue, Jan 30, 2018 at 5:22 PM, Ulrich Mueller <ulm@gentoo.org> wrote:
>> 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?
> Because having gnutls enabled and ssl disabled, if a package has
> both flags, is nonsense? What is "I want gnutls but I don't want
> support for SSL/TLS" supposed to do?
The gnutls flag doesn't have the meaning "I want gnutls". It has
the meaning "I prefer net-libs/gnutls as SSL/TLS provider". So with
USE="-ssl" the gnutls flag is a no-op, and neither the ebuild nor
the user should have to care about it.
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-01-31 9:53 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
2018-01-30 23:42 ` Gordon Pettey
2018-01-31 9:53 ` Ulrich Mueller [this message]
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=23153.37406.445528.171039@a1i15.kph.uni-mainz.de \
--to=ulm@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