Re: [go-nuts] Re: package versioning

> I suspect the annoyance of this will disappear when the team trying to > standardize this actually succeeds, and then it is always the same > metadata files. Then, you'll eventually be glad they're there. Ok. This sounds great! > go get-u github.com/spf13/cobra:v1.10.0\ >

[go-nuts] Re: package versioning

On Wednesday, October 12, 2016 at 2:04:19 AM UTC+2, Eric Johnson wrote: My view is that the general case requires putting such metadata in a > separate file for a package. > Yes, I agree with you that having multiple Go files with such comments creates repetition (having to update multiple fi

[go-nuts] package versioning

This question has been asked here a number of times, but the last time a few months ago: are there any plans to add support for package versioning (understanding VCS tags in the import paths), that is to teach `go get` to pull specified version (tag) of the package rather than the most recent v