On October 20, 2015 10:40:32 AM Dmitry Smirnov wrote:
> On Monday 19 October 2015 14:27:52 Matthew Dawson wrote:
> > I'm a lone student, so I can't really contribute financially.
> 
> Of course I don't expect sponsorship from you. :)
> 
> > What is needed for a backports effort?
> 
> Time, skills, effort and motivation. :)
Well, the second two are easy to come by, but the first two are the more 
interesting to find :)

> > Does this require building in a chroot?  I'd prefer to avoid that, as I
> > already run this in a chroot (in my specific case, Docker).
> 
> After hour of fiddling with GBP (so annoying...) I've figured it out.
> What is necessary is to add the following to "gbp.conf":
> 
> ~~~~
> [buildpackage]
> force-create = True
> overlay = True
> export-dir = ../build-area/
> ~~~~
> 
> "force-create" is optional -- it forces (re-)creation of tarball on every
> build.
> "overlay = True" actually extracts tarball into "export-dir" (so the latter
> should be given together with "overlay").
> 
> I pushed updated "debian/gbp.conf" to the repository.
Thanks for looking into this.  I had just found that option and was preparing 
an email when your email landed in my inbox.  I can confirm it works for this 
GBP addict :)

Thanks for your efforts!
-- 
Matthew

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to