Hi! On Sun, 2013-12-22 at 10:18:32 +0100, Guido Günther wrote: > I't be nice if dpkg-buildpackage would report build information (e.g. > things like the name of the generated changes file) to build-tools > invoking it. > > Doing this via a status fd would be nice[1] since we could then > implement more nice things like progress information (we'd then be able > to detect easily which dpkg-buildpackage's steps failed) without parsing > the full build output.
> [1] The status fd has the disadvantage that we need to pass it through > tools like pbuilder and sbuild as well so a file at a well known > location might be simpler. How do you see that progress information being used? Or to report what? I'm not saying a --status-fd kind of option might not be useful, just interested to know, if maybe there's something else that needs fixing instead in dpkg-buildpackage, now that I'm reworking it. For example if its error reporting leaves to be desired, then I'd rather improve that, rather than adding support for wrappers to workaround it. :) For example for 1.17.6 I'm adding hooks support, which can be useful for wrappers. > This report is triggered by #732678 where gbp failed to find the > generated changes file for a architecture independent package build > since it didn't look at the options passed to dpkg-buildpackage until > recently. For the problem described in the bug report, I think a better way to solve this is to run lintian directly from dpkg-buildpackage, which will be possible with dpkg 1.17.6, by using the new check-command support. See the following commit for further details: <http://anonscm.debian.org/gitweb/?p=dpkg/dpkg.git;a=commitdiff;h=1cef5694> Or do you need the .changes file for something else? Thanks, Guillem -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
