On Mon, May 14, 2018 at 09:23:35AM +0100, Chris Lamb wrote: > Package: git-buildpackage > Version: 0.9.8 > Severity: wishlist > > Hi, > > I just hit a little issue when working on src:plymouth in Debian. > Here, the debian/gbp.conf specifies: > > [buildpackage] > tarball-dir = ../tarballs/ > export-dir = ../build-area/ > > This overrode my setting of "export-dir = /tmp/buildd" in ~/.gbp.conf > which, whilst it appears in the build log, was rather misleading and > I actually used my muscle memory and signed a totally > unrelated .changes file at. tmp/buildd/*.changes (!). > > Two possible solutions would be: > > a) Making it not possible to override export-dir in debian/gbp.conf. > > b) Always using the value of export-dir in ~/.gbp.conf if specified, > regardless of the value in debian/gbp.conf > > c) Adding a setting to ~/.gbp.conf which toggles b), probably even a > (better named) "ignore-debian-gbp-conf-settings = export-dir,foo"
I stumbled over similar things too and while I like the symmetry between ~/.gbp.conf and debian/gbp.conf for some variables it would be nicer if maintainers would put them in ~/.gbp.conf rather than debian/gbp.conf (e.g. export-dir). This should at least be better documented. Sine the GBP_CONF_FILES env var allows to specify an arbitrary list of conf files, having a later override file would do the trick for you: export GBP_CONF_FILES=~/.gbp.conf:debian/gbp.conf:~/gbp.late.conf gbp buildpackage ... Putting export-dir in ~/gbp.conf.late should already solve your problem. Cheers, -- Guido
