From: Jaco Kroon <jaco@uls.co.za>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/3] profiles/desc: add curl_quic
Date: Fri, 21 Jun 2024 16:41:11 +0200 [thread overview]
Message-ID: <9a8a4517-0f1c-4e7c-8922-cda1823148b6@uls.co.za> (raw)
In-Reply-To: <20240621131552.526393-2-kangie@gentoo.org>
Hi,
On 2024/06/21 15:15, kangie@gentoo.org wrote:
> From: Matt Jolly <kangie@gentoo.org>
>
> The CURL_QUIC USE_EXPAND enables us to sanely manage QUIC (RFC 9000)
> backends as they are added to cURL in the future: currently there are
> two supported implementations, OpenSSL and ngtcp2, however it's likely
> that other popular TLS libraries will expose QUIC APIs over time,
> and that these will be eventually be supported by cURL (see CURL_SSL
> for examples of TLS libraries that we support) - we may as well
> get ahead of the curve here.
>
> There are already a number of other small players (i.e. OpenSSL Forks)
> exposing QUIC support for quite a while, however these have not been
> available in ::gentoo and we've only needed the one USE to enable
> for HTTP/3 and QUIC to this point.
>
> Signed-off-by: Matt Jolly <kangie@gentoo.org>
> ---
> profiles/desc/curl_quic.desc | 7 +++++++
> 1 file changed, 7 insertions(+)
> create mode 100644 profiles/desc/curl_quic.desc
>
> diff --git a/profiles/desc/curl_quic.desc b/profiles/desc/curl_quic.desc
> new file mode 100644
> index 000000000000..372bb9ce8f83
> --- /dev/null
> +++ b/profiles/desc/curl_quic.desc
> @@ -0,0 +1,7 @@
> +# Copyright 1999-2024 Gentoo Authors
> +# Distributed under the terms of the GNU General Public License v2
> +
> +# This file contains descriptions of CURL_QUIC USE_EXPAND flags for net-misc/curl
> +
> +openssl - Use OpenSSL
> +ngtcp2 - Use ngtcp2
May I suggest simply calling this USE_EXPAND QUIC_IMPL so that other
packages can potentially re-use as well?
looking through ::gentoo at least net-dns/dnsdist and net-dns/knot also
has a quic support, using ngtcp2 and/or net-libs/quiche.
With openssl 3.2 hopefully approaching stable at some point I suspect
the number of projects that will be adding quic support via one or
another channel (possibly with alternative implementations) will only
increase, thus pinning the USE_EXPAND on a single package seems
potentially short-sighted.
Kind regards,
Jaco
next prev parent reply other threads:[~2024-06-21 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 13:15 [gentoo-dev] [PATCH 0/3] net-misc/curl: add curl_quic USE_EXPAND kangie
2024-06-21 13:15 ` [gentoo-dev] [PATCH 1/3] profiles/desc: add curl_quic kangie
2024-06-21 14:41 ` Jaco Kroon [this message]
2024-06-24 2:01 ` Matt Jolly
2024-06-21 13:15 ` [gentoo-dev] [PATCH 2/3] profiles/base: make.defaults: add CURL_QUIC kangie
2024-06-21 13:55 ` Mike Gilbert
2024-06-21 13:15 ` [gentoo-dev] [PATCH 3/3] net-misc/curl: wire up live ebuild for openssl-quic kangie
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=9a8a4517-0f1c-4e7c-8922-cda1823148b6@uls.co.za \
--to=jaco@uls.co.za \
--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