Revert "nim: remove code block because it doesn't have any effect on the installation process"
It actually affetcs the build process but only on *BSD, which I did not test
nor look into properly.
sysutils/proc-cli: import proc-cli-2.2.0
proc finds, inspects and stops processes and ports. Target a process by
port (:3000), PID, name or path, see what holds a port and why it is
there, and free it. Commands that change anything ask first, preview
with --dry-run, and print JSON with stable exit codes for scripts.
NetBSD is supported upstream since 2.2.0, whose CI runs the whole test
suite on NetBSD 11. Ports come from sockstat(1) and open files from
fstat(1), both in the base system, so it has no run dependencies.
nim: remove INSTALLATION_DIRS
The INSTALLATION_DIRS is a list of directories that will be created at the beginning of the install phase. This is not needed because nim's installer automatically creates all needed directories.
nim: remove commented out codeblock
This codeblock was not needed for at least 2 years now and can pretty safely be removed. The distfiles that are needed aren't installed anyways.
nim: pass CFLAGS and LDFLAGS to nim
Nim doesn't care about CFLAGS and LDFLAGS env variables but rather has its own
--passC/--passL options to pass variables to the C Compiler or to the linker.
Find out more here:
https://nim-lang.org/docs/nimc.html
