[pkg-go] Building golang-github-google-btree from its git repo

[Matthew Dawson]

On October 19, 2015 03:11:47 PM you wrote:
> On Sunday 18 October 2015 23:39:35 Matthew Dawson wrote:
> > > Why? Etcd is as a statically linked binary so you do not need to
> > > re-build
> > > it for Jessie. Just use the package from "testing" as is. You can use
> > > Apt- Pinning technique to allow list of certain packages to be installed
> > > from "testing".
> > 
> > I generally avoid this method only because eventually I find packages that
> > start requiring newer versions of core packages that I don't want to pull
> > and keep up to date constantly.  In the past I usually got away with what
> > was available in Wheezy, but this time I have a huge dependency list.
> > 
> > If etcd (and Kubernetes in the future) can keep its runtime dependencies
> > Jessie friendly, I wouldn't have an issue doing as you suggest.
> 
> So you are building your own private backports... :)
Basically.

> 
> I'm not sure which core packages you are concerned about but in general
> since both Etcd and Kubernetes are still fairly young they are adding new
> dependencies all the time. Docker does the same...
Things like libc, systemd, etc.  If a newer one is being pulled in just 
because of a newer symbol, that isn't a great reason to upgrade those 
packages.

> 
> > If not, you could consider this a start on a backports effort :)
> 
> Maybe if this effort would be sponsored financially...
I'm a lone student, so I can't really contribute financially.  What is needed 
for a backports effort?

> 
> I agree that backports could be useful even for statically linked Golang
> software as protection from sudden changes in "testing".
> 
> > I'm happy to help in any way I can.  I haven't dug into Debian packaging
> > before, so I figured I'd start on etcd and move on to Kubernetes after. 
> > Is
> > there any specific method you'd want me to follow to work on those
> > packages?
> 
> I'd use dh-make-golang (-type="library") with passing -git_revision whenever
> upstream do formal releases. Also I add "debian/watch" file even if
> upstream do not tag yet -- it helped me more than twice already when tags
> appeared...
> > I was going to start with one of the other Go packages as a
> > template, so if you can point me at a good example I can try starting from
> > there.  I do want to finish dealing with etcd first, so that I can start
> > Kubernetes once its ready.
> 
> Although Kubernetes packaging is not published yet it is not too bad and
> will probably need only little work. But packaging all dependencies is a
> pain...
Thanks, I'll look into that once I've got etcd working.

> > I tried adding that, but it didn't seem to help.  It seems gbp doesn't
> > like
> > this repository format by default, as it assume the upstream files are
> > available.  Making it use git-pbuilder does fix it, as it builds
> > everything from the tar archive.  Google doesn't seem to talk much about
> > this.
> > 
> > I'll keep poking at this, but any other suggestions would be appreciated.
> 
> Sorry, then I think it must be the following:
> 
> ~~~~
>     [DEFAULT]
>     builder = pdebuild --debbuildopts "-i\.git -I.git $*"
> ~~~~
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).

> 
> > Ok, for reference what do you run to build from the git repository?  That
> > might help me get this going.
> 
> I just extract tarball obtained with `uscan` or `origtargz`, add "debian"
> directory and invoke `pbuilder` (or `debuild). IMHO this procedure is simple
> enough and avoids GBP which I see as unnecessary complex and demanding...
Ok, thanks, I'll keep poking at it.  I'll let you know if I figure it out, so 
the gbp.conf can be updated to work.
-- 
Matthew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3885 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20151019/8151a502/attachment-0001.bin>