K 10
svn:author
V 4
ngie
K 8
svn:date
V 27
2016-05-03T23:24:14.392671Z
K 7
svn:log
V 1220
Checkpoint next iteration for fixing tests after the release packaging merge

On reflection, using TESTS was a bit too opportunistic; I'd rather not break
things unexpectedly in downstream consumers.

In particular:
- Replace all instances of FILES/TESTS with ${PACKAGE}FILES. This ensures that
  namespacing is kept with FILES appropriately, and that this shouldn't need
  to be repeated if the namespace changes -- only the definition of PACKAGE
  needs to be changed
- Remove PACKAGE definitions where possible, i.e. where FILES wasn't used
  previously.
- Remove unnecessary TESTSPACKAGE definitions; this has been elided into
  bsd.tests.mk
- Remove unnecessary BINDIRs used previously with ${PACKAGE}FILES;
  ${PACKAGE}FILESDIR is now defined in bsd.test.mk.
- Remove unnecessary .include <bsd.own.mk>'s
- Fix installation of files under data/ subdirectories in lib/libc/tests/hash
  and lib/libc/tests/net/getaddrinfo
- Allow PACKAGE to be overridden by callers instead of forcing it to always be
  `tests`. In the event we get to the point where things can be split up
  enough in the base system, it would make more sense to group the tests
  with the blocks they're a part of, e.g. byacc with byacc-tests, etc

END