To boldly go where Node man has gone before

Re:To boldly go where Node man has gone before by chc on Wednesday May 16, 2012 @03:05PM (#3983500)

That is really interesting. Thanks for pointing that out. Can you specify specific version dependencies like you do with a full-blown package manager?

[ Parent | on HN ]

Re:To boldly go where Node man has gone before by BarkMore on Wednesday May 16, 2012 @04:07PM (#3983764)

After 'go get'ing the package, you can use git/hg/bzr to checkout the specific version you want. From there, all of the Go build tools will work as normal.

[ Parent | on HN ]

Re:To boldly go where Node man has gone before by paufernandez on Wednesday May 16, 2012 @03:58PM (#3983726)

I don't think so, but I could be mistaken. (btw, someone pointed that out as a drawback on another thread.)

What I've done sometimes is just clone the repo within a directory that appears in the GOPATH, maybe checkout a specific revision, and that solves the problem.

[ Parent | on HN ]