+1
I love gopkg.in and use it extensively - gopkg.in + tags + GOPATH is my
happy combination.
On Monday, February 26, 2018 at 1:11:21 PM UTC+3:30, Maxim Ivanov wrote:
>
> gopkg.in already "redirects" different import paths to different
> branches in your repo. You then use correct module name
gopkg.in already "redirects" different import paths to different branches
in your repo. You then use correct module name in go.mod in each branch and
it all just works.
As for "major version inside import branches" , it seems to be a cornerstone
of whole vgo proposal, so I doubt it is up for d
I feel uneasy a bit about tags (since they can come from
anywhere/any-branch). But maybe that's just being over pessimistic, about
handling/managing major versions.
And IDEs should use .mod files to reach for the source code of a definition
- which is very helpful at development time. Now there
On 26-02-2018, Kaveh Shahbazian wrote:
> It would be nice if vgo could handle something like (in .mod files)
> `pkg
>>1.2.1 branch-name-*` and the `*` part could be a major number and the
> `1.2.1` is tag. The `branch-name-*` part is a pattern for branch name.
If I understand what you mean, I
