Goenv – Go Environment Manager

To briefly explain what Goenv is, I will assume you have previously worked with Python. Basically it’s what Virtualenv is for Python. Goenv (and it’s wrapper goof) creates a folder for a new project and set the $GOPATH env variable to that folder path. At this point every time you do go get, the libraries will be installed in that specific $GOPATH.

It’s very important to use separate $GOPATH for each project, because this allow us to use different library versions for each project and avoid version conflicts.


Goenv is now installed, we will now install its wrapper goof:

Edit .bashrc (or .zshrc if you use zsh) and append these lines:

How to use it

To create a new go environment use make:

To exit the go environment use deactivate:

To use an environment use workon:

To show available environments use show:

Goenv itself is not enough to manage Go packages. It would be like using Virtualenv only and not using pip and requirements. In a future post I will explain how to use Godep.



Go: defining methods on struct types

In Go it’s possible to define methods on struct types. The syntax needed for it can be a bit strange for people that are used to define classes and methods in Java, C# etc… but once you learn it it’s quite easy to use.

In my case for example I needed something that could contain a Timer object, a string and a method that could start the timer and call a method at the end of the Timer execution. I implemented it in this way:

The key point is row 6func (timer DeviceTimer) startTimer() { … }” where I defined a method called startTimer and I specify timer DeviceTimer inside the func definition. This basically “extends” the struct DeviceTimer adding that method to it. This means that I can call that method in this way:

This is all you need to do. If you want to read more about this subject, I can suggest to read these two articles:

Note: I’m not a Go expert and these are just my personal notes I’m taking during my learning experience. I’m very keen to share my notes with everyone, but please don’t take them as notes from an expert Go developer.