On Tue, Dec 24, 2013 at 01:18:46AM +0100, Guillem Jover wrote:
> On Mon, 2013-12-23 at 11:36:19 +0100, Guido Günther wrote:
[..snip..]
> > The current unstructured output of dpkg-buildpackage leaves us only with
> > parsing the logs and looking at the exit status. Since the exit status
> > seems t
On Mon, 2013-12-23 at 11:36:19 +0100, Guido Günther wrote:
> On Mon, Dec 23, 2013 at 05:23:42AM +0100, Guillem Jover wrote:
> > 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 ge
Hi,
On Mon, Dec 23, 2013 at 05:23:42AM +0100, Guillem Jover wrote:
> 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.
On Mon, 23 Dec 2013, Guillem Jover wrote:
> > 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
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
> impleme
Package: dpkg-dev
Version: 1.17.1
Severity: wishlist
Hi,
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 thing
6 matches
Mail list logo
