> Runtime sure, and we already use that.
Do you have a pointer to this logic, It would be great to be able to update the B-D via this mecanisme like we do with cabal-debian. We should have a pip-debian which could take care of upgrading the B-D in the control file each time we integrate a new upstream version. > Test no, they aren't even specified > in an uniform way in the upstream code (it could be e.g. a > tests/requirements.txt, one or several lists of deps in tox.ini or a > custom pip install line in the CI job definition, or nothing at all if > they run tests only locally and manually). This is a pity..., it will defeat automatic packaging... > That makes sense. Or maybe it should get only the B-D annotated with > !nocheck if those exist. this is something I was wondering also. but usualy we do not tag with <!nocheck> the runtime dependecies in the B-D field. Do we need to have the run-time in the B-D in order to build the package (without running the test ?) FRed
