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\ >

Re: [go-nuts] Re: package versioning

On Thu, 13 Oct 2016 22:50:21 +0100 Nyah Check wrote: > What about creating your own copy of the package you'll like to use > in your code; something like moving the desired package version to > your own GitHub repo and calling it directly into your code. I think > this might work but may bit a bi

Re: [go-nuts] Re: package versioning

Hi everyone, What about creating your own copy of the package you'll like to use in your code; something like moving the desired package version to your own GitHub repo and calling it directly into your code. I think this might work but may bit a bit harder to deal with in the longterm. Will like

Re: [go-nuts] Re: package versioning

On 10/12/16 2:32 AM, Peter Vypov wrote: 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 cr

[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] Re: package versioning

On Tuesday, October 11, 2016 at 5:55:23 AM UTC-7, Peter Vypov wrote: > > 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`