From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: blueness@gentoo.org
Subject: Re: [gentoo-dev] RFC: net-misc/curl: HTTP/3 support
Date: Thu, 10 Oct 2019 16:38:02 -0400 [thread overview]
Message-ID: <CAJ0EP41OHPqESGVuX8MuHdieYnLP1Hy0=un1ykAfAPbpbAL1Bg@mail.gmail.com> (raw)
In-Reply-To: <12708cbd76bff9f20725c1c9deffa614@gentoo.org>
On Thu, Oct 10, 2019 at 4:03 PM Craig Andrews <candrews@gentoo.org> wrote:
>
> I'm working on getting HTTP/3 support in place for curl:
> https://github.com/gentoo/gentoo/pull/12920
>
> Yes, HTTP/3 isn't final yet. But we're Gentoo - that shouldn't stop us!
>
> My proposal involves:
> * A new USE_EXPAND, CURL_HTTP3, with two values: nghttp3 and quiche
Why do we need a USE_EXPAND for this? Will more than one package ever use it?
If it's only ever going to be referenced by net-misc/curl, just add
local USE flags.
next prev parent reply other threads:[~2019-10-10 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 20:03 [gentoo-dev] RFC: net-misc/curl: HTTP/3 support Craig Andrews
2019-10-10 20:38 ` Mike Gilbert [this message]
2019-10-10 20:48 ` Michał Górny
2019-10-11 16:20 ` Craig Andrews
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='CAJ0EP41OHPqESGVuX8MuHdieYnLP1Hy0=un1ykAfAPbpbAL1Bg@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=blueness@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