[aur-general] Exact purpose of check()

Julien Nicoulaud julien.nicoulaud at gmail.com
Wed Jan 2 14:44:46 UTC 2019


Hi,

There is a bit of debate at the borgmatic package (
https://aur.archlinux.org/packages/borgmatic) about what check() should do.
The upstream borgmatic project uses tox to execute its tests. tox creates
an isolated python virtualenv with the correct dependency versions and
executes tests in there.

The original maintainer thinks check() should not use tox so that tests can
be run against the system installed dependencies. But this is not so easy
to do, an attempt was made by installing the python package into an
isolated directory just for tests, but even then it seems to conflict with
an existing borgmatic installation.

Another way of seeing things is that check() should just run tests the way
it is intended by upstream, it is for testing the build artifacts are
correct, not for testing it will run correctly on the system where it is
built. By this logic check() should just run tox, and correct dependency
versions can be enforced by using version ranges in "depends".

Any advice on this ?

Cheers,
Julien


More information about the aur-general mailing list