Sean Whitton <spwhit...@spwhitton.name> writes: > I believe that Ian's intention is that the build tool should be > configured to put build products somewhere else, and then dgit should be > told where they are using --build-products-dir. I.e. you have > ~/.gbp.conf telling gbp where to put build products, and then
> % dgit --build-products-dir ~/foo gbp-build This appears to not work. In fact, there appears to be no way to get dgit to work with gbp-buildpackage if you set an export-dir in your ~/.gbp.conf (at least in some brief experiments). Even with that flag, dgit writes some (but not all) of its output files in the parent directory (pieces of the source package and the downloaded dsc file of the previous release), and then aborts because it can't find the right files. It appears to be doing pieces of the build outside of gbp-buildpackage, since I know gbp-buildpackage will always write all of its files in my configured export-dir. I could be missing something, but I tried a few different iterations before just giving up and using dgit build, and I couldn't figure out any way to get all of the build product in the right location and get dgit push to find it. I unfortunately didn't save a full transcript of my session, but I tried: $ dgit -wgf --build-product-dir ../build-area gbp-build $ dgit -wgf --build-product-dir ../build-area push and then again with expicitly setting --export-dir on the gbp-build command line in case dgit was overriding it somehow. My ~/.gbp.conf has: [buildpackage] export-dir = ../build-area/ tarball-dir = ../tarballs/ -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
