From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.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:22:59 +0100 [thread overview]
Message-ID: <23152.65107.266869.334200@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20180130221106.11245-1-mgorny@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2984 bytes --]
>>>>> On Tue, 30 Jan 2018, Michał Górny wrote:
> Correct the description of SSL/TLS-related flags to match their modern
> use. USE=ssl is a feature flag that enables support for SSL/TLS,
> while USE=gnutls and USE=libressl are implementation toggling flags.
> Unify the descriptions a bit. Make sure to mention both SSL and TLS
> to avoid confusion. Inform about the necessity of enabling USE=ssl
> in both implementation flags, and replace 'might' with 'if present'.
> ---
> profiles/use.desc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> diff --git a/profiles/use.desc b/profiles/use.desc
> index 43423a017a5f..4ac5d5ad6136 100644
> --- a/profiles/use.desc
> +++ b/profiles/use.desc
> @@ -119,7 +119,7 @@ gmp - Add support for dev-libs/gmp (GNU MP library)
> gnome - Add GNOME support
> 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?
> gphoto2 - Add digital camera support
> gpm - Add support for sys-libs/gpm (Console-based mouse driver)
> gps - Add support for Global Positioning System
> @@ -179,7 +179,7 @@ libcaca - Add support for colored ASCII-art graphics
> libedit - Use the libedit library (replacement for readline)
> libffi - Enable support for Foreign Function Interface library
> libnotify - Enable desktop notification support
> -libressl - Use dev-libs/libressl as SSL provider (might need ssl USE flag), packages should not depend on this USE flag
> +libressl - Use dev-libs/libressl instead of dev-libs/openssl as SSL/TLS provider (requires USE=ssl if present), packages should not depend on this USE flag
Same here.
> libsamplerate - Build with support for converting sample rates using libsamplerate
> libwww - Add libwww support (General purpose WEB API)
> lirc - Add support for lirc (Linux's Infra-Red Remote Control)
> @@ -319,7 +319,7 @@ sox - Add support for Sound eXchange (SoX)
> speex - Add support for the speex audio codec (used for speech)
> spell - Add dictionary support
> sqlite - Add support for sqlite - embedded sql database
> -ssl - Add support for Secure Socket Layer connections
> +ssl - Add support for SSL/TLS connections (Secure Socket Layer / Transport Layer Security)
> startup-notification - Enable application startup event feedback mechanism
> static - !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically
> static-libs - Build static versions of dynamic libraries as well
> --
> 2.16.1
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-01-30 23:23 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 [this message]
2018-01-30 23:39 ` Kristian Fiskerstrand
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=23152.65107.266869.334200@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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