On Tue, Jan 24, 2012 at 10:28:18PM -0800, Russ Allbery wrote: > Andrew Pollock <apoll...@debian.org> writes: > > > I just got onto the git-pbuilder bandwagon, and was briefly confused as > > to where my resulting build went, because when I use pdebuild, the > > results wind up in the default location of /var/cache/pbuilder/result, > > and I'm quite happy with that. > > > git-pbuilder seems to forcibly supply a "--buildresult .." with no way > > to override that. > > That's because the way this normally works is that git-buildpackage runs > git-pbuilder and expects that behavior, because that means the build ends > up in build-area (or whatever you have configured).
So historically I didn't know about git-pbuilder and run git-buildpackage something like this: git-buildpackage --git-builder="pdebuild --debbuildopts '-i\.git -I.git' -- --basepath /var/cache/pbuilder/base-unstable.cow" I may yet go back to doing that but jamming it in my gbp.conf for brevity. > If you tell *git-buildpackage* that you want your builds to end up in > /var/cache/pbuilder/result (via --git-export-dir), I believe everything > works, but at the cost of dropping the source package and unpacked tarball > into that directory as well. I don't know if that would be a problem. I'm not convinced that will work, but I'll give it a try. The man page says "Export the current branch head (or the treeish object given via --git-export to directory before building." > I don't think I ever considered the possibility that people would want the > build-area and the place where the built debs end up to be different. I'm not following. The build-area is off in a pbuilder chroot somewhere isn't it? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
