search

couchbaselabs / cbft

*THIS PROJECT HAS MOVED* from couchbaselabs TO: https://github.com/couchbase/cbft -- no further development will be done here on couchbaselabs/cbft
Other
27 stars 5 forks source link

consider switching to from go-manifest to godep, gb, etc #6

Closed mschoch closed 9 years ago

mschoch commented 10 years ago

I haven't used it yet myself, but it appears to be functionally very similar, with the benefit it that is being used by others in the go community.

https://github.com/tools/godep

steveyen commented 9 years ago

Hat-tip to Marty, looks like there even a newer thing, gb, that might be the eventual winner.

Lazily, I think we should let it all settle down in the go community first before switching.

steveyen commented 9 years ago

Or, it looks like the laziest, leading maneuver is to await new golang 1.5 related features.

mschoch commented 9 years ago

There is also the issue that once we begin integration with Couchbase server, the repo file will be the authoritative source of locked revisions and cloned repos.

Some thought should be given to how (if?) this will be supported for use outside of Couchbase server.

steveyen commented 9 years ago

As I'm scrubbing old bugs, I think this is close'able as no need to do anything more.

afaik, we've been able to maintain build'ability via standalone cbft via standard "go get", and also optionally with more build tags (such as what we do via Makefile).

And, the manifests / repo approach of Couchbase Server integrated builds seems to also work.

Going to 1.5, too, and picking up whatever vendoring that provides, will just be the natural, expected par for the course if we need vendoring, so I figure we don't need a ticket to remind us about that.