I have a project github.com/perillo/xxx, that currently is available only locally. The project has two commands `cmd/a` and `cmd/b`, and some packages with common API use by the two commands.
`cmd/a` reads an external file and produces a file that is then used by `cmd/b`. `cmd/b` and the common API have no external dependencies, but `cmd/a` depends on a (relatively) large module. Currently I'm using a different `modfile` for `cmd/a`; it works but the user needs to clone the repository, instead of simply use `go install`. Today I decided to try making `cmd/a` a separate module, using go1.18 workspace mode. What I did was: `go work init; go work use -r .` `cd cmd/a; go mod init; go mod tidy` The unexpected problem is that the go tool reported an error, since it tried to get the github.com/perillo/xxx module from the module cache, that of course does not have it. Is this a limitation of workspace mode, or am I doing something wrong? Thanks Manlio -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/a5b49ccd-463d-467e-92ed-1f569ee0a936n%40googlegroups.com.
