> I've dropped using @builddep@ in general within the packages I'm > involved to achieve exactly what Andrey has written, I want to detect > broken or missing dependencies, broken tests by changed dependencies in > other depending packages. And don't want to get this hidden by packages > that are within @builddep@ that potential pull in the other then needed > packages.
exactly > Using @builddep@ is mostly not useful for testing Python packages. does the python tools provide a way to get the runtime dependencies or the test dependencies of a package ? This would allow to automatize a lot'of our packaging job, upgrade etc.. > So yes, need to figure out which packages then you want to have listed > in d/t/control to make the tests pass. yes. I will use the doc snipset and customize it to have the right dependencies. But I am wondering if the best would not be to have something more declarative like the extra_dependencies in order to supersede the full dependencies instead of just adding more dependencies. Fred
