file, which was neglected previously. Pass the toolset to the test script
with the --toolsets option (i.e., plural, not singular). Add a date to
the log file to better identify when tests were run and how long they took.
the test directory after successfully running the tests. Thus, users
can expect that the resources used for running the tests will only be
temporarily required during the tests. In addition, add a note about
where the test results can be found.
tests may be run in any directory writable by the user. It also means that
there will be no cleanup of the test directory if the package is removed.
Specifically, the following changes were made.
- Install most package files into PREFIX/libdata/boost-test-suite.
- Teach boost-test-suite to copy files from there into the test directory.
- Add a command line option (-b) to define the test directory. By default,
the directory is determined by the value of BOOST_TEST_BASEDIR at the
time the package is built. This may be configured in mk.conf, but is
/var/boost otherwise.
- Reverse the sense of the -c command line option to mean that the test
directory SHOULD be cleaned. Previously, cleaning was done by default.
- Rely on tool definitions from pkgsrc (except ftp and hostname).
- Include USE_TOOLS+=ftp to obtain dependency.
- Allow users to customize test directory within ${PREFIX}.
In addition, enhance debug output to print command lines and add a safeguard
to ensure that the test directory actually exists to avoid dumping files
in inappropriate places.
