Jan,
To clarify a bit, "world" used to be everything under $GOPATH/src. Since
gophers can expect at some point to see $GOPATH go away the directory I now
refer to as "world" is just a local/private version of my github.com/hotei
repository with about 250 or so subdirs that represent individual
On Thu, Mar 18, 2021 at 4:51 PM Brian Candler wrote:
> OK. I'll just point out that if the repo contains a set of related packages,
> then normally you'd only put a go.mod at the top level.
I think the OP never mentioned a repository but "world". I infer that
means all the repositories the OP
OK. I'll just point out that if the repo contains a set of related
packages, then normally you'd only put a go.mod at the top level.
For an example of this in action, see the "testify" group of packages:
https://github.com/stretchr/testify/
The subdirectories are separate packages. For example
Brian,
Looks like a case of "pilot error". After tinkering a bit more it started
to work. Each directory has its own go.mod file. Took a little while to
figure out what the module wanted to see for versioning but that's seems to
be sorted now. Still have a large number of projects to conve
What error do you see?
Are your subdirectories independent modules in their own right (i.e. they
have their own "go.mod"), or just separate packages within the same module
(go.mod only exists at the top level)? Normally the latter is what you
want.
On Wednesday, 17 March 2021 at 17:57:55 UTC
