Russel,

Just two add a quick doc reference: 

The general capability being discussed here is called "module queries".

This section of the doc is probably worth a quick read or re-read:

 https://golang.org/cmd/go/#hdr-Module_queries

Module queries provide a fair amount of flexibility, and allow you to do 
something like 'go get foo@sometag' or 'go get foo@somebranch' (or 
equivalently, have 'require foo sometag'  or 'require foo somebranch' in 
your go.mod).

However, your module query will be resolved and recorded in go.mod in a 
canonical form (usually a semver tag or a pseudo-version that includes a 
commit hash).  

My understanding is that at least part of the intent behind the resolution 
to a canonical form is related to the desire to maintain a total ordering 
over recorded versions (so that it is clear for example which recorded 
versions are "later" than other recorded versions).

In any event, hope the doc reference helps,

--thepudds

On Thursday, November 15, 2018 at 5:39:10 AM UTC-5, Paul Jolly wrote:
>
> > > The `dev` in that documentation is intended to be a branch name. If 
> that 
> > > module doesn't actually *have* a branch named `dev`, it won't work. 
>
> Thanks, Bryan. 
>
> > ... 
> > 
> > Hopefully there is a way of this getting updated as master/HEAD gets 
> more 
> > commits. 
>
> Not automatically, no. go get X@master will bring you up-to-date. 
>
> https://github.com/golang/go/issues/26964 is about the ability to 
> track a branch in a more systematic way. 
>
> > Now I just have to find out why: 
> > 
> >    module arcamclient 
> > 
> > is causing the error: 
> > 
> > can't load package: package arcamclient: unknown import path 
> "arcamclient": cannot find module providing package arcamclient 
>
> See https://github.com/golang/go/issues/27503#issuecomment-437052752 
>
>
> Paul 
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to