Add explicit dependencies on several tools we need

[copumpkin]

I left unzip and git implicit, but made sure they had loud comments next to them.

Should fix #1335, #1328, and #1234

Also, regarding the autoconf,

[copumpkin]

The duplication between here and release.nix made me uncomfortable but they do seem pretty duplicatey already.

[domenkozar]

What if Nix is compiled on different machine than it's used? Or is the purpose to hardcode nix store paths for those tools (autotools is magic)?

[copumpkin]

@domenkozar yes, it would include store paths for those tools whenever built by Nix, and they'd thus end up in the runtime closure of Nix (a good thing IMO). And if someone builds it on a non-Nix system we'll just embed non-store paths and nothing is lost.

@edolstra any thoughts? I saw that since I submitted this PR, you already did lsof a little differently, and are not depending on lsof in release.nix. That will probably work in practice on macOS, but it'd be nice to depend explicitly on the package.

Still curious how to do things like builtins.fetchgit in a pleasant manner. On one hand, #693 could be one answer. On the other hand, #520 would allow all these builtin fetchers to be defined outside of Nix, at the cost of a more complicated staged evaluation/build model

[stale]

I marked this as stale due to inactivity. → More info

[stale]

I closed this issue due to inactivity. → More info

[fricklerhandwerk]

@copumpkin I think it's unfortunate the bot was closing pull requests. Are you still interested in working on this? The addressed issues are still hitting Nix beginners.