On 18/10/15 13:07, Axel Beckert wrote: > Source: nghttp2 > Severity: wishlist > > I installed nghttp2 because I wanted an HTTP/2 client on the commandline > on my laptop. I was surprised thatthe server is started by default in > such a mixed server/client package. > > So I suggest to split up nghttp2 into nghttp2-server (which contains > server and proxy) and nghttp2-client. nghttp2 could then become a > metapackage pulling in both, nghttp2-server and nghttp2-client. > > Alternatively not starting the server by default would also suffice but > may confuse people who already run such a server and rely on it. > > In general, I consider splitting up the package makes more sense. In the > HTTP/1.x world you have way more clients than servers. Everyone would be > surprised if e.g. Debian's libwww-perl package did not only provide the > lwp-download, GET and HEAD commandline tools, but also start a server > based on the according Perl modules for HTTP servers which it also > contains.
Hi Axel, I totally agree, I was surprised myself when I encountered the package for the first time. This is a historic relic of the packaging process and it is on my todo list for some time :). The naming is unfortunate in other places too: the client binary is really called 'nghttp', not 'nghttp2' and so on. I like your idea, but I'd add another split: - nghttp2-client - nghttp2-server - nghttp2-proxy For backwards compatibility, the 'nghttp2' meta package would pull all of this. Does it seem reasonable? Btw., you can now use 'curl' with '--http2' option. Cheers, Tomasz
signature.asc
Description: PGP signature
