I’m glad it works for you too. I just added more subdirectory packages to the
Module and everything is working well. I haven’t tried to access the Modules’s
packages from another Module, although I plan to. I’ll let you all know what
works.
> On Apr 1, 2020, at 1:58 PM, David Riley wrote:
>
>
This is actually a fairly neat solution! I might look at using that from here
on out.
How well does it work if something else (also with access to your private
repository) tries to include your module?
- Dave
> On Apr 1, 2020, at 11:47 AM, Dave Mazzoni wrote:
>
> With all the examples out
With all the examples out there and a little experimentation, I found the
solution I needed. Here's the tree from the 'top' directory:
├── dfs
│ ├── dfs.go
│ ├── dfs_test.go
│ └── go.mod
├── first.go
├── go.mod
└── ModuleDFS
Here are the file contents starting from the top of the directory s
I have become totally confused about using local modules. Please help --
I'll try to keep this short:
I have a package (dfs) and a main package. I tried laying things out an
using _ for local packages from your excellent post on github, but I still
cannot get things to build correctly.
I got the
