I have been thinking about this bug. Sean: > Ian suggests that maybe this should be the other way around: when > you set --build-products-dir foo, dgit will pass > --git-export-dir=foo to invocations of gbp.
The problem with this is that this won't affect the user's own invocations of gbp. There is a converse problem with the original idea of dgit asking gbp: this is all very well for `dgit gbp-build' but what about (say) `dgit push-source' where dgit doesn't know you're using gbp. dgit could ask gbp iff gbp is installed but that would mean that if you have a ~/.gbp.config specifying export-dir, the behaviour of dgit would depend on whether gbp was actually installed. Not nice. The goal surely is for the user to have to configure the bpd in only one place. That should affect dgit, gbp, pbuilder, sbuild, origtargz/git-deborig, etc. (In each case if and when the user users each of these commands.) This ought to work without depending on any of these utilities, and without depending on git, etc. I think this means we need a Debian-wide env var or a config file. Ian. -- Ian Jackson <[email protected]> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
