Interesting. It has pretty much the same objectives as mu godeps tool, but executed slightly differently.
Some thoughts: - the "save/restore" syntax is nice. - it doesn't currently support bzr. - the json Godeps file is nice but currently lacks some information (it would be nice if it included the revision control system and the revision number, if applicable) - the "godep go" command is great, but makes for an awkward development experience where the source code that you're compiling and using is not necessarily the code that you see. Updating in place has its own problems though. - it should use full hg revision ids, not the short form. - it has no tests. - the ImportPath entry in the Godeps file is somewhat arbitrary - it seems to include one arbitrary package from each repo. - it looks like it won't diagnose properly certain unusual GOPATH configurations (when a GOPATH entry contains a package that is a sub-path of a package found in a previous GOPATH entry). Probably not too much of an issue in practice. In general, I'd say go for it - I'll be happy to have one less thing to maintain, and the more of the community that's behind a single tool, the better. On 12 September 2013 02:09, David Cheney <[email protected]> wrote: > https://groups.google.com/d/msg/golang-nuts/8NJq6jTIpas/Vpf-KZtVu9MJ > > Unless there are strong disagreements, I'd like to spike using this > tool on juju-core. > > Dave > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
