TEST_DEPENDS on itself?

[Christian Weisgerber]

Mathieu Arnold:

> > I'm working on a port that can't run its regression tests out of
> > the build or stage areas.  The command to be tested will call
> > submodules with compiled in absolute paths (/usr/local/libexec/...).
> > So this port bla/foo would require to be already installed for
> > testing:
> > 
> > TEST_DEPENDS=   foo:bla/foo
> > 
> > The foo command will call /usr/local/libexec/foo/foo-helper.  If
> > the latter isn't there, foo won't run.
> 
> Well, you cannot have recursive dependencies, so a port cannot depend on
> itself.  What about if you chroot in STAGEDIR to run the tests?

The stage area is far too incomplete.

So, no TEST_DEPENDS.  A simple Makefile rule "test: install"?
I see there is precedence in the tree:

cad/opencascade/Makefile:regression-test:    install
math/rkward-kde/Makefile:regression-test:    install
math/arpack++/Makefile:test: install
math/py-fpylll/Makefile:do-test: install
math/mumps4/Makefile:regression-test:        install
math/jags/Makefile:check test: install
math/mumps/Makefile:regression-test: install
devel/aap/Makefile:test: install
french/aster/Makefile:regression-test:       install
science/gnudatalanguage/Makefile:regression-test:    install
textproc/sowing/Makefile:regression-test: install
net/py-libdnet/Makefile:regression-test: install
net/mpich2/Makefile:regression-test: install

-- 
Christian "naddy" Weisgerber                          naddy at mips.inka.de