Quoting PICCA Frederic-Emmanuel
<frederic-emmanuel.pi...@synchrotron-soleil.fr>:
It install by default the build dependencies. which is not what
peoples are doing when they install the packages.
It should be possible to define the autopkgtest dependencies. This
way we could catch missing dependencies in python-<modules>
dependencies.
Is it possible ?
I believe (didn't check so many packages), in most cases
installing the build dependencies is the better option:
1. There might be testing frameworks to install as b-d, but
not as Depend.
2. Many unit test suites check various variants and optional
behaviour, that might be separated in different binary
packages (think of myapp-postgres and myapp-mariadb, etc.)
Maybe as an option for some packages?
Or a different kind of test, running on top of piuparts?
