To boldly go where Node man has gone before

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

If I wanted a specific tag or release, I would just download that revision in the GOPATH directories, and refer to the package directly, instead of through the github URL.

[ Parent | on HN ]

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

Kind of a clunky way to handle versioning though. In Lein (for example), adding

    [noir "1.2.0"]

ensures I'm always grabbing the same version. In Go, appears the only way to guarantee this is to check in the full source of the library alongside your own in your repo.

[ Parent | on HN ]

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

I wish Leiningen would also handle bleeding edge dependencies as easily as rebar eg:

    {deps, [
      {quoted, "1.0.3",
        {git, "git://git.corp.smarkets.com/quoted.erl.git", {tag, "1.0.3"}}},
      {proper, ".*",
        {git, "git://git.corp.smarkets.com/proper.git", {branch, "master"}}}
    ]}.

[ Parent | on HN ]

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

This plugin[1] looks like what you're looking for.

[1] https://github.com/tobyhede/lein-git-deps

[ Parent | on HN ]

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

"You will also need to manually add the checked-out project's dependencies as your own (the plugin simply checks out the code, it doesn't recursively resolve dependencies)."

I've seen this plugin before but its not particularly useful without dependency checking. It's a start though. I'll have to look at leiningen to see if it exposes hooks for that sort of thing.

[ Parent | on HN ]