On Monday, December 12, 2016 10:57:20 AM CST Peter Pentchev wrote: > On Sun, Dec 11, 2016 at 08:22:09PM -0600, Steve M. Robbins wrote:
> > Alternatively: if the logic was all in dh (to skip both dh_auto_test > > and override_dh_auto_test), then it would not need to be in > > dh_auto_test at all. > > It may still need to be in dh_auto_test for packages that still do not > use the override targets at all, but invoke the dh_* commands explicitly > from the "build", "binary", etc targets. None of mine do, but I bet that > there are still some in the archive :) You're suggesting someone would use dh_auto_test from within a binary target? Interesting use case. My feeling is that DEB_BUILD_OPTIONS represent global build options, so I think I'd design it into dh rather than individual tools. You're right that it would be a breaking change, but I think one could use a debhelper compatibility level to remove the functionality from the tools. -Steve
signature.asc
Description: This is a digitally signed message part.
