Ian Jackson writes ("Re: Bug#844125: dgit: Built-in support for pbuilder [and 1
more messages]"):
> 1. I think many pbuilder users expect to be able to set a build
> products directory. Currently there are bugs in dgit's
> --build-products-dir option; probably, too many hardcoded "../"
> (which should be fairly easy to fix, but rather whack-a-mole-ish).
I had a thought about this whack-a-mole game. We could change the
test suite to (unless specified otherwise by the specific test) set a
build-products-dir. And have a check sat the end that the toplevel
test tmp has not been polluted.
I may implement this if it would be useful, but I think I need to know
what the interaction between build-products-dir and .origs ought to be
like:
> 2. I am not sure where origs should go when --build-products-dir is
> being used. Is it pbuilder practice to put them in the build produts
> dir or in .. ? If they go in build-products-dir then we need to do
> something extra in dgit, because many dgit operations - not limited to
> build operations - either consume or produce origs; and then, we would
> want a config setting. Or maybe dgit should always do what pbuilder
> does and the build-products-dir should be precisely that setting.
> (Either way, that's more whack-a-mole removing "../".)
Ian.
