Sigh. On Wed, Feb 05, 2014 at 12:59:23PM +0000, Neil Williams wrote: > Using packages to support upstream development is a common problem and > this is exactly where things get awkward.
No, it is not a *problem*; it is a *method* of doing things. It is not your place (nor mine) to question another person's methods of doing things; especially not if said methods are done outside of Debian, as is here the case. Enforcing Debian Policy in the tools (i.e., not allowing to do things contrary to debian policy, even if that's wanted) is a *bad* idea, in all cases. [...] > > Also, using git-buildpackage is difficult. > > The build is done by sbuild, which does not call git-buildpackage. > > Not true. There are options to use debuild or pdebuild or > dpkg-buildpackage in-place. > > e.g. I use: > > [DEFAULT] > #builder = git-pbuilder > builder = debuild > cleaner = fakeroot debian/rules clean > pristine-tar = True > > [git-buildpackage] > export-dir = ../build-area/ > tarball-dir = ../tarballs/ Even if so, this increases the complexity of the system, and requires people to learn yet another tool to Just Do what was previously possible with no extra fluff. It's okay for a tool (like dpkg) to warn if something doesn't look right. It's not okay for a tool (like dpkg) to pretend to be smarter than the person operating said tool. -- This end should point toward the ground if you want to go to space. If it starts pointing toward space you are having a bad problem and you will not go to space today. -- http://xkcd.com/1133/ -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
