nixpkgs/pkgs/tools/networking/drill/default.nix

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

43 lines
918 B
Nix
Raw Normal View History

2021-10-20 07:18:09 +00:00
{ lib
, stdenv
2020-04-15 18:08:20 +00:00
, rustPlatform
, fetchFromGitHub
, pkg-config
, openssl
2020-05-03 09:20:00 +00:00
, Security
2020-04-15 18:08:20 +00:00
}:
rustPlatform.buildRustPackage rec {
pname = "drill";
2023-04-19 07:10:10 +00:00
version = "0.8.3";
2020-04-15 18:08:20 +00:00
src = fetchFromGitHub {
owner = "fcsonline";
repo = pname;
rev = version;
2023-04-19 07:10:10 +00:00
sha256 = "sha256-4y5gpkQB0U6Yq92O6DDD5eq/i/36l/VfeyiE//pcZOk=";
2020-04-15 18:08:20 +00:00
};
2023-04-19 07:10:10 +00:00
cargoHash = "sha256-96eUCg0mzgUFLOKxpwRfzj1jH2Z+aDohBTztvRVWln0=";
2020-04-15 18:08:20 +00:00
2021-10-20 07:18:09 +00:00
nativeBuildInputs = lib.optionals stdenv.isLinux [
pkg-config
];
treewide: use lib.getLib for OpenSSL libraries At some point, I'd like to make another attempt at 71f1f4884b5 ("openssl: stop static binaries referencing libs"), which was reverted in 195c7da07df. One problem with my previous attempt is that I moved OpenSSL's libraries to a lib output, but many dependent packages were hardcoding the out output as the location of the libraries. This patch fixes every such case I could find in the tree. It won't have any effect immediately, but will mean these packages will automatically use an OpenSSL lib output if it is reintroduced in future. This patch should cause very few rebuilds, because it shouldn't make any change at all to most packages I'm touching. The few rebuilds that are introduced come from when I've changed a package builder not to use variable names like openssl.out in scripts / substitution patterns, which would be confusing since they don't hardcode the output any more. I started by making the following global replacements: ${pkgs.openssl.out}/lib -> ${lib.getLib pkgs.openssl}/lib ${openssl.out}/lib -> ${lib.getLib openssl}/lib Then I removed the ".out" suffix when part of the argument to lib.makeLibraryPath, since that function uses lib.getLib internally. Then I fixed up cases where openssl was part of the -L flag to the compiler/linker, since that unambigously is referring to libraries. Then I manually investigated and fixed the following packages: - pycurl - citrix-workspace - ppp - wraith - unbound - gambit - acl2 I'm reasonably confindent in my fixes for all of them. For acl2, since the openssl library paths are manually provided above anyway, I don't think openssl is required separately as a build input at all. Removing it doesn't make a difference to the output size, the file list, or the closure. I've tested evaluation with the OfBorg meta checks, to protect against introducing evaluation failures.
2022-03-25 15:33:21 +00:00
OPENSSL_LIB_DIR = "${lib.getLib openssl}/lib";
2022-03-24 00:59:21 +00:00
OPENSSL_DIR="${lib.getDev openssl}";
2021-10-20 07:18:09 +00:00
buildInputs = lib.optionals stdenv.isLinux [
openssl
] ++ lib.optionals stdenv.isDarwin [
Security
];
2020-04-15 18:08:20 +00:00
meta = with lib; {
2020-04-15 18:08:20 +00:00
description = "HTTP load testing application inspired by Ansible syntax";
homepage = "https://github.com/fcsonline/drill";
2021-10-20 07:18:09 +00:00
license = licenses.gpl3Only;
maintainers = with maintainers; [ Br1ght0ne ];
2020-04-15 18:08:20 +00:00
};
}