pkgsStatic.cryptsetup: don't --enable-static-cryptsetup

--enable-static-cryptsetup adds binaries suffixed with .static,
e.g. cryptsetup.static, and those binaries have extra flags set to
enable them to be built statically.  It doesn't change how the main
binaries are built — they're compiled correctly because pkgsStatic
sets up all the necessary compiler flag anyway.  So as far as I can
tell, all --enable-static-cryptsetup gets us is duplicate binaries
that take up disk space unnecessarily.
This commit is contained in:
Alyssa Ross 2022-01-24 13:01:46 +00:00
parent 4762a265d4
commit e28c5cd7ac

View file

@ -31,8 +31,6 @@ stdenv.mkDerivation rec {
"--enable-cryptsetup-reencrypt"
"--with-crypto_backend=openssl"
"--disable-ssh-token"
] ++ lib.optionals stdenv.hostPlatform.isStatic [
"--enable-static-cryptsetup"
];
nativeBuildInputs = [ pkg-config ];