Packaging Go 1.5 applications for Debian-like systems

The original question, https://stackoverflow.com/questions/15104089/packaging-golang-application-for-debian, was asked over three years ago, when Go was statically linking executables.

Now, with the new Go 1.5 Release, whose release note says,

> Changes to the linker enable distributing Go packages as shared libraries to link into Go programs, and building Go packages into archives or shared libraries that may be linked into or loaded by C programs

I headed to Debian GoPackaging wiki, but only to find out that it has not been updated to Go 1.5 yet, maybe the wiki is not maintained, or maybe not, but,

I just want to know, if I want to package a tool that depends on nothing but the official Go packages, how should I take advantage of the shared libraries, instead of building my app into a humongous statically linked executable?

I know the official answer may take some time, but I can wait.

Thanks to Braiam's answer, I moved a bit further.

• I followed the blog to the step head -100 debian/**/*, but my output is completely different from the blog's. Mine is just the following. Anyone knows why and how to fix?

    $ head -100 debian/**/*
    3.0 (quilt)
  

• I tried to run gbp buildpackage --git-pbuilder but bumped into error:

    gbp:info: Building with (cowbuilder) for sid
    Base directory /var/cache/pbuilder/base.cow does not exist
    gbp:error: 'git-pbuilder' failed: it exited with 1
  

• I checked and verified that I already have cowbuilder & pbuilder installed:

    ii cowbuilder  amd64 pbuilder running on cowdancer
    ii pbuilder  all personal package builder for Debian packages
  

What's wrong? This pbuilder thing is new to me as I build Debian/Ubuntu Package with Docker.

The easiest method is to use dh-make-golang and verify/correct the autogenerated files. Otherwise you must follow Debian Packaging Guide and create debian/* directory and editing the control and rules file to match the examples.