Sean Whitton writes ("Bug#863582: Allow configurable build directory"):
> On Sun, Jun 18, 2017 at 07:47:14PM -0700, Russ Allbery wrote:
> > Even with that flag, dgit writes some (but not all) of its output files in
> > the parent directory (pieces of the source packa
On Sun, Jun 18, 2017 at 07:47:14PM -0700, Russ Allbery wrote:
> > % 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 ex
Sean Whitton 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
>
Control: forcemerge 857316 -1
Sean Whitton 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
On Sun, May 28, 2017 at 01:38:30PM -0700, Russ Allbery wrote:
> I use git-buildpackage for all of my package building, and one reason why
> is that I deeply dislike the default Debian behavior of cluttering the
> parent directory with random package build files. git-buildpackage has
> always suppo
Package: dgit
Version: 3.10
Severity: wishlist
I use git-buildpackage for all of my package building, and one reason why
is that I deeply dislike the default Debian behavior of cluttering the
parent directory with random package build files. git-buildpackage has
always supported configuring a bui
6 matches
Mail list logo
