Hi, On Tue, 2008-04-15 at 09:15:24 +0200, Raphael Hertzog wrote: > Package: dpkg-dev > Version: 1.14.18 > Severity: wishlist > User: [EMAIL PROTECTED] > Usertags: dpkg-buildpackage > > See #476100 for the reason. The lack of features in dpkg-bp resulted > in a fork of it...
Yeah, been thinking about that, while considering what would be good to merge back (I probably missed it on the TODO update :). > I think it's clear that it's best to extend dpkg-bp to support everything > that people need. The minimal set of features to add is the hook support > so that debuild can at least become a wrapper of dpkg-buildpackage again. > > But I would favor going further: > - also generate a .build file (with a mid-term interest to > upload it with each binary build) The problem with that one is that we cannot enable it by default (yet), as that would not play nice with debuild, I don't think sbuild would be a big problem but it's doing logging by itself, and it migth want to be able to at least disable that, to avoid doing double logging, which might be significant on multi MiB log packages. > - also cleanup the environment by default Hmm, we should probably not clean some of the build related ones, related to Robert Luberda's message on 476100. > - add a configuration file so that we don't have to always retype > "[EMAIL PROTECTED]" or "-us -uc -i -I" if we don't want to > (the default options should appear in the build log however) IIRC Frank proposed something like this some time ago? I think that'd be good, but we should probably print the defaults used, so that people don't get unexpected surprises. regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
