Hi Tim and thanks!
I'm just using a random upstream repository(github) and trying to package
it using the Debian tools. Actually dh-make-golang does all the magic and
now I'm able to create the .deb with the binaries and sources in it. I
don't know why yesterday it wasn't including the binaries in the .deb
package, but now is working like a charm. Today I was messing it with
cowbuilder and pbuilder stuff and it works. I'll take a closer look on how
those tools work under the hood.
Question: If some projects have their dependencies in the vendor dir, why
dh-make-golang skip those? Does Debian packages never ship the deps in that
Anyway, thanks for the interest.
2016-07-19 16:24 GMT-05:00 Potter, Tim (HPE Linux Support) <
> On 20 Jul 2016, at 1:51 AM, Erick Cardona <erick0zcr....@gmail.com> wrote:
> > Hi everyone,
> > I'm currently packaging a go project for educational purposes. Now I'm
> able to build a package using the tools dh-make-golang and gbp(Awesome
> tools!!). I was able to build a binary-only package but manually. I was
> wondering if using gbp I could obtain a .deb which contains the binaries of
> the package? Like the docker-engine.deb which contains the binaries of
> > PS: I'm really new to packaging, but looking further to join the Debian
> Hi Erick. The best way to make a new Debian package from a Go library is
> with dh-make-golang
> and gbp so you're on the right track there.
> Can you push what you've done so far to a git repo somewhere for review?
> I'm happy to
> take a look and give feedback.
Pkg-go-maintainers mailing list