Consider adding installation prerequisites about gmailctl HOT 5 CLOSED

From looking at travis it seems to be testing go at stable and tip, currently meaning 1.11.1 and devel +a2381f5966.

Should I assume that only latest stable version mentioned at https://golang.org/doc/devel/release.html is supported, with dev Travis build serving as warning about incoming breaking changes?

from gmailctl.

You need to first go get the package this way:

go get github.com/mbrt/gmailctl/cmd/gmailctl
go install github.com/mbrt/gmailctl/cmd/gmailctl

Also make sure that the install path is in your $PATH.

I don't know exactly what's the minimum version that works with this package, but 1.6 should be OK.

from gmailctl.

I think that explicit

go get github.com/mbrt/gmailctl/cmd/gmailctl

would be helpful for go newbies - especially as go get has some useful complaints like complaining about unset $GOPATH. I plan to make PR adding it to instructions, hopefully it is OK.

Apparently, according to prometheus/collectd_exporter#37 (comment) 1.7 go is minimum (though 1.7 may be not enough, I need to test it)

mateusz@grisznak:~/Desktop/tmp$ echo $GOPATH
/home/mateusz/Documents/install/gopath_target
mateusz@grisznak:~/Desktop/tmp$ go get github.com/mbrt/gmailctl/cmd/gmailctl
package context: unrecognized import path "context" (import path does not begin with hostname)

and later

mateusz@grisznak:~/Desktop/tmp$ go install github.com/mbrt/gmailctl/cmd/gmailctl
../../Documents/install/gopath_target/src/github.com/mbrt/gmailctl/cmd/gmailctl/cmd/init_cmd.go:4:2: cannot find package "context" in any of:
	/home/mateusz/Documents/install/gopath_target/src/github.com/mbrt/gmailctl/vendor/context (vendor tree)
	/usr/lib/go-1.6/src/context (from $GOROOT)
	/home/mateusz/Documents/install/gopath_target/src/context (from $GOPATH)

from gmailctl.

You are right, I did that already when I saw this issue (See updated README). I suspect the Gmail APIs want new releases of Go, although they don't specify which one.

from gmailctl.

I did that already when I saw this issue (See updated README)

I believe that it fixes this issue...

Thanks!

from gmailctl.