> Then why are they in a monorepo?
>
> AFAIK monorepos for strictly controlled dependenies and easier refactorings.
>
> If two part needs different versions for something common, then they should
> live and evolve separately.
This is a subset of a larger mono-repo. This repo has sources for
abou
9:16:04 PM
To: Tamás Gulácsi
Cc: golang-nuts
Subject: Re: [go-nuts] go modules and local packages
> Use one go.mod pee repo.
That won't be possible. It is a monolithic repo. svc1 and svc2 may
need two different versions of a common dependency.
--
You received this message because
> Use one go.mod pee repo.
That won't be possible. It is a monolithic repo. svc1 and svc2 may
need two different versions of a common dependency.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving e
> You could try moving mylib to your $GOPATH/src/, and
> import "mylib"
> in the services.
I tried that but could not get `go run cmd/svc1.go` from trying to
checkout a non-existent url (for the `mylib`). Can you share the
contents of the `go.mod` file for svc1 and mylib ?
--
You received th
You could try moving mylib to your $GOPATH/src/, and
import "mylib"
in the services.
On Sat, 8 Aug 2020, 20:21 Sankar, wrote:
> Hi
>
> I have a monolithic source repository that is NOT in git, mercurial etc.
>
> The directory structure is:
>
> root
> |
> |--- mylib
> | | --- mylib.go
Use one go.mod pee repo.
--
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
Hi
I have a monolithic source repository that is NOT in git, mercurial etc.
The directory structure is:
root
|
|--- mylib
| | --- mylib.go
| | --- go.mod
|--- svc1
| | --- go.mod
| | --- cmd
| | svc1.go
|--- svc2
| | --- go.mod
| | ---
