seq(1) just made source, but just in case you run into pesky tests that
want to run gnu tools, I know we added the (g) prefix to make them
(in some cases) harder to misuse instead of the base tool, let me remind
you that there is a directory called ${WRKDIR}/bin that gets put at
the TOP of the PATH for anything ports-dependent.

That's generally used to obtain specific behavior like enforce whichever
C/C++ compiler we want (or to neuter chmod/chown/install during fake).

It can also be used to great effect during make test.

A simple set of recipes like


TEST_DEPENDS += sysutils/coreutils

pre-test:
        ln -sf /usr/local/bin/gseq ${WRKDIR}/bin/seq


was enough to repair some tests.

In some cases of gnu vs base tools, this can be trickier: configure that 
auto-detects tools that will be used later in testing may require to move 
those dependencies (and symlink) into BUILD_DEPENDS/pre-configure.  
In such case, it will be necessary to check that the dependency
doesn't get hardcoded needlessly into a RUN_DEPENDS.  Other times,
you'll find out that the detected tool does end up as a config.h/Makefile
variable after configure, in which case it's pretty simple to
redirect it to the tool you actually need through TEST_FLAGS.

Reply via email to