I'm not sure if we want to include tools in nixpkgs that probably just have a single user, since there's a non-zero cost to including new packages, namely maintenance, hydra build time and for NixOS modules it even slows down everybody's nixos-rebuild. See also the discussion in https://discourse.nixos.org/t/we-need-more-defined-guidelines-for-package-inclusion/3592

Maybe NUR is a better place to put such packages, or eventually as Flakes.

reopened in honour of the 1st anniversary of the v1 release 4 years ago

converted to draft until the test can be sorted out
main issues there are:

1. actually networking the two machines
2. extracting the MAC, IPv4 and/or IPv6 addresses from the second machine, to check if they're detected on the first

actually waiting for the ping to succeed seems to be enough for the other machine's hostname to show up

ideally i'd get the addresses out of the other machine and check for those, but this will do as a basic test

i'm intentionally ignoring the failing nixpkgs-check-by-name check
this adds 3 very closely related packages all based on the same source
i'd like to keep them grouped in 1 directory, rather than add 3 by-name directories

@evils See https://github.com/NixOS/nixpkgs/tree/master/pkgs/by-name#recommendation-for-new-packages-with-multiple-versions then to resolve the CI failure.

@infinisil huh, thanks, i didn't think to look there because i didn't know by-name was now a requirement
(i don't see that in CONTRIBUTING.md)
(note that jumping to that anchor doesn't seem to work (because of the loading time of such a long page?))

the recommendation there does not provide enough context for me to be able to use it
(where should inherit be used?, what's meant with a local package set (local where?), foo_1 refers to ../tools, wouldn't this be ../to/tools?)
is there an example package that already does this?
(just grepping for inherit yields a bit too much noise to find such)