Many moons ago, I wrote about setting up a Go environment in Ubuntu. After writing that post, I dropped Go development for nearly a year. Today I run the Indy Golang meetup, and soon I’ll be starting a new work project where I’ll be recommending a Go-based tech stack. I’ve learned a thing or two about Go and managing its dependencies since I wrote that initial blog post, and I intend to give a short presentation to my meetup about my recent findings. Before I do, I thought I’d write a preliminary blog post detailing the tools I use to keep my Go environment sane.

Installing Go

The easiest way to install Go in Ubuntu is through <code class="codecolorer ruby default">aptitude. However, the default version in the Ubuntu repos gets stale fast. I found a tool similar to <code class="codecolorer ruby default">rvm for downloading and installing local versions of Go called gvm. For better or worse, <code class="codecolorer ruby default">gvm is installed through a bash script. Fortunately, it doesn’t require sudo:

$ bash < <(curl -s -S -L https://raw.githubusercontent.com/moovweb/gvm/master/binscripts/gvm-installer)

At this point I removed all my previous finaglig with <code class="codecolorer ruby default">$GOROOT and <code class="codecolorer ruby default">$GOPATH from my dot files. You can use <code class="codecolorer ruby default">gvm listall to see all available versions of Go. As of the writing of this blog post, <code class="codecolorer ruby default">go1.4.1 is the latest release; however, go1.4 is the most recent release available with <code class="codecolorer ruby default">gvm. I’m not sure when the list is updated, but I have confidence that it is fairly regular. To install a Go and set it as the default Go:

$ gvm install go1.4 –default $ which go /home/lrp/.gvm/gos/go1.4/bin/go

Managing Packages

This is where I come to a fork in the road: <code class="codecolorer ruby default">gvm, the tool we used to install the desired version of Go, has a concept of pkgset similar to <code class="codecolorer ruby default">rvm gemset. However, I find the syntax for using a pkgset tiresome every time I come into a directory. I prefer something more automatic. As an additional pain, <code class="codecolorer ruby default">gvm does not provide a mechanism for installing dependencies from a list of known dependencies. I sought out other tools to address these pains and found gpm and gvp.

<code class="codecolorer ruby default">gpm is a tool used to manage Go packages. It reads in a file called <code class="codecolorer ruby default">Godeps which contains a list of packages with versions and can install them from their individual sources. I’m currently infatuated with <code class="codecolorer ruby default">gpm as it addresses a lot of concerns I had when initially learning Go: shared local dependencies, unclear versioning, and installing dependencies from a fresh clone. Install <code class="codecolorer ruby default">gvm and <code class="codecolorer ruby default">gvp:

$ pushd /tmp $ git clone https://github.com/pote/gvp.git && cd gvp $ ./configure && sudo make install $ cd /tmp $ git clone https://github.com/pote/gpm.git && cd gpm $ ./configure && sudo make install $ popd

We can follow two paths here: using <code class="codecolorer ruby default">gvm pkgset or using a local <code class="codecolorer ruby default">.godeps directory to store our dependencies discretely. For these examples, I’ll create a directory called <code class="codecolorer ruby default">gotest with a single file in it:

package main import “github.com/go-martini/martini” func main() { server := martini.Classic() server.Get(“/”, func() string { return ”

Hello, world!

” }) server.Run() }

Method 1: gvm pkgset alongside gpm

Create and start using a new pkgset:

$ gvm pkgset create gotest $ echo $GOPATH /home/lrp/.gvm/pkgsets/go1.4/global $ gvm pkgset use gotest $ echo $GOPATH /home/lrp/.gvm/pkgsets/go1.4/gotest:/home/lrp/.gvm/pkgsets/go1.4/global

What this means is that we are now using our <code class="codecolorer ruby default">gotest pkgset as default, but the global pkgset will be used to dig up any missing packages. In order to install any dependencies, we need to create a <code class="codecolorer ruby default">Godeps file for <code class="codecolorer ruby default">gpm to consume. Our application from above has a dependency on <code class="codecolorer ruby default">go-martini, so let’s add a dependency to <code class="codecolorer ruby default">v1.0 in our Godeps file:

github.com/go-martini/martini v1.0

After you run <code class="codecolorer ruby default">go build to verify that the dependencies aren’t installed, run <code class="codecolorer ruby default">gpm install to pull the required packages into your specified pkgset. Run <code class="codecolorer ruby default">go build again and revel in your own brilliance.

That was pretty great, right? The only issue is remembering to type <code class="codecolorer ruby default">gvm pkgset use gotest every time you restart your terminal or switch projects. Otherwise, <code class="codecolorer ruby default">gvm is practically a replacement for one of my favorite ruby tools <code class="codecolorer ruby default">rvm.

Method 2: gpm and gvp

<code class="codecolorer ruby default">gpm is intended to be similar to <code class="codecolorer ruby default">npm a package management tool for NodeJS. The author suggests using a tool called <code class="codecolorer ruby default">gvp to set the <code class="codecolorer ruby default">GOPATH without much thought. If we start a fresh terminal in our example directory, we can use <code class="codecolorer ruby default">gvp to set up our <code class="codecolorer ruby default">GOPATH:

$ echo $GOPATH /home/lrp/.gvm/pkgsets/go1.4/global $ source gvp $ echo $GOPATH /home/lrp/Projects/2015/gotest/.godeps:/home/lrp/Projects/2015/gotest

You can note the difference in our <code class="codecolorer ruby default">GOPATH here relative to <code class="codecolorer ruby default">gvm: we will be using our current directory as a source of code in addition to a local <code class="codecolorer ruby default">.godeps directory. Go ahead and add <code class="codecolorer ruby default">.godeps to your <code class="codecolorer ruby default">.gitignore file or equivalent. We can use the same <code class="codecolorer ruby default">Godeps file as before:

github.com/go-martini/martini v1.0

We run <code class="codecolorer ruby default">gpm install to install the dependencies to our local <code class="codecolorer ruby default">.godeps directory.

I prefer this method to using pkgsets. I’ve had better luck building projects with complicated structures, and it’s a lot easier for me to run <code class="codecolorer ruby default">source gvp than it is to remember the name of my pkgset. Both methods work pretty well and give me warm fuzzies about managing my dependencies. I’m certain that as Go continues to mature more solutions will come available. I’ve also been researching using Docker with gpm only, which requires very little tweaking to what I’ve already discussed here.

This post was originally posted here:https://larry-price.com/blog/2015/01/18/managing-a-go-environment-in-ubuntu/#disqus_thread

Managing a Go Environment in Ubuntu

Installing Go

Managing Packages

Hello, world!

Method 1: gvm pkgset alongside gpm

Method 2: gpm and gvp