<div dir="ltr"><div>Here are a couple binary-only packages:</div><div><br></div><a href="http://anonscm.debian.org/cgit/pkg-go/packages/etcd.git/">http://anonscm.debian.org/cgit/pkg-go/packages/etcd.git/</a><br><div><a href="http://anonscm.debian.org/cgit/pkg-go/packages/heartbleeder.git/">http://anonscm.debian.org/cgit/pkg-go/packages/heartbleeder.git/</a><br></div><div><a href="http://anonscm.debian.org/cgit/pkg-go/packages/skydns.git/">http://anonscm.debian.org/cgit/pkg-go/packages/skydns.git/</a><br></div><div><br></div><div>Why do you need an install file at all if you’re just dealing with a binary-only package?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 13, 2015 at 8:22 PM, Chas Williams III <span dir="ltr"><<a href="mailto:Charles.Williams@brocade.com" target="_blank">Charles.Williams@brocade.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">See attached. I can build the golang-stringutils package fine.<br>
myutil builds but I am unable to create a binary package that only<br>
contains the utility myutil. I don't need to ship myutil's as a<br>
development package.<br>
<br>
I have been unable to find an example of dh-golang used to build a<br>
binary only package.<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, 2015-05-13 at 12:04 -0600, Michael Stapelberg wrote:<br>
> Without seeing your packaging it’s very hard to help. Maybe taking a<br>
> look at the existing pkg-go packages helps?<br>
><br>
> On Wed, May 13, 2015 at 7:21 PM, Chas Williams III<br>
> <<a href="mailto:Charles.Williams@brocade.com">Charles.Williams@brocade.com</a>> wrote:<br>
> I think I have it figured out now. I wasn't setting DH_GOPKG<br>
> on the<br>
> non-library package.<br>
><br>
> How do you write an *.install file to match file paths? The<br>
> files don't<br>
> seem to be installed in the temporary root and the typical<br>
> paths I would<br>
> use don't seem to work.<br>
><br>
> On Tue, 2015-05-12 at 14:06 -0600, Michael Stapelberg wrote:<br>
> > Why woulud the build system need to write<br>
> to /usr/share/gocode? You<br>
> > shouldn’t need to touch your dependencies during build.<br>
> ><br>
> ><br>
> > Can you make your packaging available? Without seeing the<br>
> code, it’s<br>
> > hard to help.<br>
> ><br>
> > On Tue, May 12, 2015 at 7:44 PM, Chas Williams III<br>
> > <<a href="mailto:Charles.Williams@brocade.com">Charles.Williams@brocade.com</a>> wrote:<br>
> > Hello,<br>
> ><br>
> > I have managed to produce a golang Debian package,<br>
> but I still<br>
> > can't<br>
> > seem to figure out how to use this package to build<br>
> my Go<br>
> > application.<br>
> ><br>
> > Buildsystem/<a href="http://golang.pm" target="_blank">golang.pm</a> says want I want to hear:<br>
> ><br>
> ><br>
> ><br>
> ############################################################################<br>
> > # Symlink all available libraries<br>
> from /usr/share/gocode/src<br>
> > into our<br>
> > # buildroot.<br>
> ><br>
> ############################################################################<br>
> ><br>
> > But _link_contents() doesn't really seem to do that.<br>
> It<br>
> > symlinks<br>
> > the directories, but shouldn't it really create the<br>
> > directories and<br>
> > symlinks the source files (*.go) since it's unlikely<br>
> the build<br>
> > system<br>
> > can write to /usr/share/gocode?<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Best regards,<br>
> > Michael<br>
><br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> Best regards,<br>
> Michael<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Best regards,<br>Michael</div>
</div>