Update golang to version 1.0.2

[fd]

Go 1.0 and 1.0.1 have some bugs in their toolchain (go get './...' doesn't work as expected)

[michaelklishin]

@fd please update gvm to 1.0.2 and it will be provisioned on travis a few days after.

[fd]

It seams that gvm doesn't need updating... just run gvm install go1.0.2

[michaelklishin]

Ok. It seems to need aliasing support, though, so that it can be switched to as go1. It would be great if you could add that feature before go1.1 is out.

[fd]

I'll give it a go 😉

[michaelklishin]

Awesome, thanks! 1.0.2 should be deployed tomorrow or so.

[fd]

Great!

Could you elaborate a bit on what you're trying to achieve with the aliasing feature.

I'm thinking on doing some thing like this.

# list all aliases
$ gvm alias list
my-go -> go1.0.2

# add a new alias
$ gvm alias add go1.0.2 my-go

# use an alias
$ gvm use my-go
Using go1.0.2

# remove an alias
$ gvm alias rm my-go

[michaelklishin]

The goal is to let developers specify multiple runtime versions that do not depend on the specific point version. E.g. if you have

go:
  - go1
  - go1.1

then we should be able to upgrade go1 to 1.0.3 without asking you to update your .travis.yml. For Ruby, for example, this feature is used a lot more aggressively: we have 2 versions of JRuby and Rubinius, built with different
Ruby version (both JRuby and Rubinius can work in either 1.8 or 1.9 mode). Go won't need that but the ability to
switch versions without knowing the exact patch level is essential to support multiple versions of a runtime.

[fd]

I'm waiting for my gvm PR to get accepted. In the mean time, here is commit adding alias support in travis-cookbooks

[michaelklishin]

Should be live already (without aliasing but with 1.0.2). Give it a try.

[fd]

go test './...' still doesn't work (see http://travis-ci.org/#!/fd/options/builds/2519570; were the boxes rolledback?)