nixpkgs/pkgs/by-name/na/nat-traverse/package.nix
aleksana 571c71e6f7 treewide: migrate packages to pkgs/by-name, take 1
We are migrating packages that meet below requirements:

1. using `callPackage`
2. called path is a directory
3. overriding set is empty (`{ }`)
4. not containing path expressions other than relative path (to
makenixpkgs-vet happy)
5. not referenced by nix files outside of the directory, other
than`pkgs/top-level/all-packages.nix`
6. not referencing nix files outside of the directory
7. not referencing `default.nix` (since it's changed to `package.nix`)
8. `outPath` doesn't change after migration

The tool is here: https://github.com/Aleksanaa/by-name-migrate.
2024-11-09 20:04:51 +08:00

39 lines
1.3 KiB
Nix

{ lib, stdenv, fetchurl, perl }:
stdenv.mkDerivation rec {
pname = "nat-traverse";
version = "0.7";
src = fetchurl {
url = "https://www.speicherleck.de/iblech/nat-traverse/nat-traverse-${version}.tar.bz2";
sha256 = "0knwnqsjwv7sa5wjb863ghabs7s269a73qwkmxpsbngjw9s0j2ih";
};
nativeBuildInputs = [ perl ];
installPhase = ''
mkdir -p $out/bin $out/share/man/man1
cp nat-traverse $out/bin
gzip -c nat-traverse.1 > $out/share/man/man1/nat-traverse.1.gz
'';
meta = with lib; {
description = "NAT gateway traversal utility";
longDescription = ''
nat-traverse establishes direct connections between nodes which are
behind NAT gateways, i.e. hosts which do not have public IP addresses.
This is done using an UDP NAT traversal technique. Additionally, it's
possible to setup a small VPN by using pppd on top of nat-traverse.
nat-traverse does not need an external server on the Internet, and it
isn't necessary to reconfigure the involved NAT gateways, either.
nat-traverse works out-of-the-box.
'';
homepage = "https://www.speicherleck.de/iblech/nat-traverse/";
license = licenses.gpl3Plus;
platforms = platforms.all;
maintainers = [ maintainers.iblech ];
mainProgram = "nat-traverse";
};
}