Add `gnubin` dir for all programs that are prefixed with `g`

[me_cameronkatri.com]

Summary

Create a directory at ${PREFIX}/gnubin for symlinks to all utilities that are prefixed with a g to be used without the prefix. This is useful when project's build system needs a GNU userland but doesn't check for the binaries with a g prefix.

[bapt]

We do have BINARY_ALIAS for that if that is needed, so I do not see what gnubin brings in here. For me I am not convince this brings anything useful.

[arrowd]

I agree with @bapt here. Making gfoo program available as foo during build will probably make the port require is as foo during runtime too. This, in turn, would require to add gnubin to PATH and this is another big can of worms.

[me_cameronkatri.com]

In D30167#677453, @bapt wrote:

We do have BINARY_ALIAS for that if that is needed, so I do not see what gnubin brings in here. For me I am not convince this brings anything useful.

I meant for when not building in ports.

[arrowd]

In D30167#677459, @me_cameronkatri.com wrote:

I meant for when not building in ports.

The argument stays. If the software you are building uses autotools, you can usually pass things like SED=/usr/local/bin/gsed to the configure script. Same goes for CMake buildsystem and probably meson.

[me_cameronkatri.com]

However, when cross-compiling for a gnu system it will then look for the wrong bin in runtime.

[arrowd]

In D30167#677599, @me_cameronkatri.com wrote:

However, when cross-compiling for a gnu system it will then look for the wrong bin in runtime.

That's right, but such use-case seems to be quite specific. Are you doing such cross-compilations yourself?

[jakehfreebsd_gmail.com]

I agree with @arrowd , I think this is too large a change for such a small use case. I think that if you want to cross-compile something on FreeBSD to GNU, you should probably work on improving the software being cross-compiled to support prefixes, as opposed to modifying FreeBSD to work with non-prefixing.