On Sat, Jun 17, 2017 at 1:04 PM, Guillem Jover <guil...@debian.org> wrote: > Yes, because dpkg-buildpackage will run the debian/rules clean target, > which by policy requires the Build-Depends/Conflicts to be satisfied.
For most packages I build, dpkg-buildpackage -S running clean works fine without all build-dependencies installed. I manually pass -nc when I don't feel like installing the extra debhelper addons like pkg-kde-tools. > I don't see any compelling argument presented here besides the implicit > "it breaks my workflow!" [W]. Yes, but I think it's an extremely common workflow on Ubuntu as I already explained. If you're unwilling to do this for Debian, it may still make sense on Ubuntu. The odd part is that the behavior changed for me when I installed Ubuntu 17.10 Alpha but not with 17.04 (dpkg 1.18.10) so it feels like a recent "regression" on Ubuntu but I can't explain why I wasn't affected for the past year in 16.10 and 17.04. I did workaround the issue by changing my build configuration to use -d by default. Thanks, Jeremy Bicha
