nixpkgs/pkgs/development/libraries/ngtcp2/gnutls.nix
Vladimír Čunát 9e1040188a
ngtcp2-gnutls: 0.13.0 -> 0.13.1
https://github.com/ngtcp2/ngtcp2/releases/tag/v0.13.1
With 0.14.x there are some knotd issues
which haven't been figured out yet.
2023-04-04 09:58:14 +02:00

54 lines
1.5 KiB
Nix

{ lib, stdenv, fetchFromGitHub
, autoreconfHook, pkg-config
, gnutls
, cunit, ncurses, knot-dns
}:
stdenv.mkDerivation rec {
pname = "ngtcp2";
version = "0.13.1";
src = fetchFromGitHub {
owner = "ngtcp2";
repo = "ngtcp2";
rev = "v${version}";
sha256 = "sha256-bkTbnf7vyTxA623JVGUgrwAuXK7d8kzijOK1F4Sh4yY=";
};
outputs = [ "out" "dev" ];
nativeBuildInputs = [ autoreconfHook pkg-config ];
buildInputs = [ gnutls ];
configureFlags = [ "--with-gnutls=yes" ];
enableParallelBuilding = true;
doCheck = true;
nativeCheckInputs = [ cunit ]
++ lib.optional stdenv.isDarwin ncurses;
passthru.tests = knot-dns.passthru.tests; # the only consumer so far
meta = with lib; {
homepage = "https://github.com/ngtcp2/ngtcp2";
description = "an effort to implement RFC9000 QUIC protocol.";
license = licenses.mit;
platforms = platforms.unix;
maintainers = with maintainers; [ vcunat/* for knot-dns */ ];
};
}
/*
Why split from ./default.nix?
ngtcp2 libs contain helpers to plug into various crypto libs (gnutls, patched openssl, ...).
Building multiple of them while keeping closures separable would be relatively complicated.
Separating the builds is easier for now; the missed opportunity to share the 0.3--0.4 MB
library isn't such a big deal.
Moreover upstream still commonly does incompatible changes, so agreeing
on a single version might be hard sometimes. That's why it seemed simpler
to completely separate the nix expressions, too.
*/