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. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
