all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@crash.cx>
To: Christian Grothoff <grothoff@gnunet.org>,
	Marius Bakke <mbakke@fastmail.com>,
	Tobias Geerinckx-Rice <me@tobias.gr>,
	guix-devel@gnu.org, gnunet-developers@gnu.org
Subject: Re: 14/14: gnu: gnurl: Add HTTP/2 support.
Date: Sat, 24 Feb 2018 22:12:46 +0000	[thread overview]
Message-ID: <20180224221246.iq3rvmg4svstbode@abyayala> (raw)
In-Reply-To: <20180224220736.aj7fmydekiiffa5d@abyayala>


[-- Attachment #1.1: Type: text/plain, Size: 2624 bytes --]

ng0 transcribed 3.1K bytes:
> Christian Grothoff transcribed 3.7K bytes:
> > On 02/24/2018 10:43 PM, ng0 wrote:
> > > Marius Bakke transcribed 1.6K bytes:
> > >> Tobias Geerinckx-Rice <me@tobias.gr> writes:
> > >>
> > >>> nckx pushed a commit to branch core-updates
> > >>> in repository guix.
> > >>> +             ("nghttp2" ,nghttp2 "lib")
> > >> As far as I can tell, we don't have an nghttp2 package yet :-)
> > > 
> > > 
> > > Why? I don't even intend to support http/2 with gnURL.
> > > gnURL is not cURL. Are there any reasons why this should be build in?
> > 
> > Well, the idea of Gnurl was to be reasonably minimal and to avoid the
> > kitchen-sink dependencies (and unpredictability wrt SSL support) of the
> > original Curl. I personally don't see a need for http/2 at this point
> > (bad), especially as it adds additional dependencies (very bad) and
> > would not be available equally on all systems Gnurl runs on (very very bad).
> 
> I agree here and wasn't 100% sure on http/2. I just check the list of abilities
> to not build only when I do the releases.
> 
> > My recommendation remains that Curl should be modified to dlopen()
> > extensions/plugins to load protocol/TLS-support extensions on-demand.
> > Until that happens,
> 
> This will take some time, cURL has some of your early criticism on their
> todo list last time I've read the todo list, but we might be faster switching
> to wget2. Only time will tell.
> 
> > my view is that we should be very, very conservative
> > in terms of features we add to avoid creating another kitchen-sink. For
> > those with kitchen-sink requirements, there is always Curl...
> 
> Okay. With this in mind, could anyone with access to the branches in Guix
> revert this commit?
> Furthermore, should I add a comment above the gnurl package definition wrt
> the goals of gnURL and that it already gets build the way it is intended
> to?

Well there's one fixme, which is the same as for cURL in Guix: Get the certificates
working. patches in gnURL accepted, as well as anything that's better than my last
attempt in gnURL in Guix which broke builds on some systems.
I don't have the time to think of solutions for this at the moment.

> > _______________________________________________
> > GNUnet-developers mailing list
> > GNUnet-developers@gnu.org
> > https://lists.gnu.org/mailman/listinfo/gnunet-developers
> 
> 
> -- 
> ng0 ::  https://n0.is | https://crash.cx
> A88C8ADD129828D7EAC02E52E22F9BBFEE348588



-- 
ng0 ::  https://n0.is | https://crash.cx
A88C8ADD129828D7EAC02E52E22F9BBFEE348588

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 162 bytes --]

_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@gnu.org
https://lists.gnu.org/mailman/listinfo/gnunet-developers

  reply	other threads:[~2018-02-24 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180220150633.1503.67041@vcs0.savannah.gnu.org>
     [not found] ` <20180220150637.273A720447@vcs0.savannah.gnu.org>
2018-02-24 21:31   ` 14/14: gnu: gnurl: Add HTTP/2 support Marius Bakke
2018-02-24 21:43     ` ng0
2018-02-24 21:59       ` Christian Grothoff
2018-02-24 22:07         ` ng0
2018-02-24 22:12           ` ng0 [this message]
2018-02-25 15:42           ` Tobias Geerinckx-Rice

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=20180224221246.iq3rvmg4svstbode@abyayala \
    --to=ng0@crash.cx \
    --cc=gnunet-developers@gnu.org \
    --cc=grothoff@gnunet.org \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.