Hello Mattia, On Sat, Nov 12, 2016 at 07:31:59PM +0000, Mattia Rizzolo wrote: > With my pbuilder maintainer hat on, I'm happy to provide all the help > you need, included (if you see the need) changes on pbuilder's side :) > > > > DISCLAIMER: I'm not (yet) a dgit user, but always be a fun of the > concept, and it reached a point where I don't need to throw away my > workflow, and I'm happy of the experience I had while sponsoring Sean's > package. I'll probably start to use it more soon ^^
I'm thinking of working on this. I think it will be straightforward. The only possibility for complexity is if I've missed something about how pbuilder works. Would the following work: 1. user runs `dgit <dgit opts> pbuilder <pbuilder opts>` 2. dgit builds a source package and _source.changes in its own way 3. dgit invokes `pbuilder build foo_1.2.3-1.dsc <pbuilder opts>` 4. dgit invokes mergechanges to merge its _source.changes and the binary .changes produced by pbuilder. This is exactly the pattern of `dgit sbuild`, so we can probably refactor the cmd_sbuild() sub and then trivially add cmd_pbuilder(). Let me know if you think this will work. -- Sean Whitton
signature.asc
Description: PGP signature
