[pkg-go] pkg-go reference implementions

[Geert Stappers]

On Wed, May 18, 2016 at 08:03:02AM -0700, Tianon Gravi wrote:
> On 17 May 2016 at 10:56, Geert Stappers <stappers at stappers.it> wrote:
> > Which go lang package could be considered as an reference implementation?
> 
> Most packages are at least started via "dh-make-golang" (and often
> dh-make-golang is used to regenerate newer upstream tarballs), so the
> majority should have a very similar structure.  I would definitely
> recommend checking out the tool if you're looking to package software
> written in Go, even more especially if upstream does not tag releases.
> 
> If you want a simple library package example, "golang-pault-go-config"
> is pretty bare-bones.
> 
> If you're rather looking for a binary package example, "rawdns" isn't
> very complex, but something like "runc" or "containerd" might be
> better to show both a tool/binary and a -dev package in one source.
> 
> I wouldn't say these are necessarily "canonical" examples, but they're
> a few that I was able to find fairly quickly by scanning my own local
> checkouts of pkg-go repos for ones that have very few files.
> 
> Hope that helps!
> 

Yes, it did help. Thanks.

I could `debcheckout` 3 out of 4 of the packages. Probably due running
"testing" and not "unstable" for the latest and greatest.

I'll study those packages and will pay attention on the existence of
-dev packages.


Cheers
Geert Stappers
-- 
$ history | tail -n 10
  535  cd src
  536  debcheckout golang-pault-go-config
  537  debcheckout rawdns
  538  debcheckout runc
  539  aptitude search runc
  540  debcheckout golang-github-opencontainers-runc-dev
  541  echo fatal: repository 'https://anonscm.debian.org/pkg-go/packages/runc.git/' not found
  542  debcheckout containerd
  543  history | tail -n 20
  544  history | tail -n 10