can we rely on the fact that alternative dependencies of test cases are
resolved with priority from left to right?
My use case is as follows: package why3 has a test case for testing
interaction with cvc4. The latter, however, is not available on all
architectures, and the test case should not fail if that is the case
. So the idea is to have in the test case a dependency "cvc4|why3",
with the intention that cvc4 will be installed whenever it is available.
Then, the test script checks whether cvc4 is indeed installed, and
just does "exit 0" when this is not the case.
Would this work? If not, is there a recommended way to make a test
case not fail when a dependency is not satisfiable?
-Ralf (please cc me in replies)