public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: 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 22:48:01 +0200	[thread overview]
Message-ID: <d117d65f915d3b09151cd3f249ca8c5baa36e844.camel@gentoo.org> (raw)
In-Reply-To: <CAJ0EP41OHPqESGVuX8MuHdieYnLP1Hy0=un1ykAfAPbpbAL1Bg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

On Thu, 2019-10-10 at 16:38 -0400, Mike Gilbert wrote:
> 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.

+1 to local.  I know that curl mainainers have a history for adding
redundant USE_EXPANDs for extra user complexity but that's not a reason
to make things even worse.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2019-10-10 20:48 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
2019-10-10 20:48   ` Michał Górny [this message]
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=d117d65f915d3b09151cd3f249ca8c5baa36e844.camel@gentoo.org \
    --to=mgorny@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