Error when building executable (via bin/build) (Ubuntu 13.10 64bit) about cli

[kytrinyx]

That is odd. It builds fine on my machine. It sounds like it suggests that it should be os.Args(), but when I try that, it blows up locally.

Which version of Go are you using? I've got 1.1.2:

$ go version
go version go1.1.2 darwin/amd64

[drueck]

I've got the same version, more/less:

davidco: etl ✭ (master) ✗ go version
go version go1.1.2 linux/amd64

I wish I could be more helpful in troubleshooting, but I don't know anything about go. However, I am speculating that the thing it is complaining about is the assignment err := App.Run(os.Args) because when I deleted the err := part (and the following code that dealt with err) it ran fine. Hope that helps!? :)

[kytrinyx]

Interesting, thanks!

[kytrinyx]

Oh. Wait!

This is possibly a dependency thing. Try go get -u github.com/codegangsta/cli. The cli library did a major version bump recently.

[drueck]

Ah, that did the trick! I ran a go get before trying the build, but I didn't realize you had to use the -u flag to force the update. Interesting. Cool, thanks! :)

Just out of curiosity, do you know if you can just do go get -u to force the update of all the dependencies? Or is that not desirable? (I'm not sure how the dependencies are versioned/controlled with go get). I'm just wondering if there's something we could add to the process in the README to handle a case like this?

[kytrinyx]

I'm assuming go get -u would work, but I haven't tried it yet.

Dependency management is very complex, and it doesn't seem to be a solved problem. See http://nathany.com/go-packages/

If it becomes a big problem, we should probably vendor these things. I don't think it will become a real problem, especially since the only production dependency (cli) just hit 1.0.

[drueck]

Gotcha. Yeah, sounds like dependency management is far from figured out for go! But you're right, it might not be a big issue like you said since cli is now at 1.0 and theoretically has a more stable api.

Just out of curiosity I tried out go get -u and it did something sort of odd:

davidco: exercism-cli (master) go get -u
davidco: exercism-cli (c795bc7) git status
# HEAD detached at origin/master
nothing to commit, working directory clean

Looks like it checked out origin/master for exercism/cli. So, if you did that, you'd have to subsequently do a git co master to get back to where you want to be.

I guess it's probably fine to just leave the README as it is and wait to see if more people run into stuff like this before bothering to clutter up the instructions with edge cases.

[kytrinyx]

Yeah, that sounds reasonable. Thanks for helping think about it!