Oops. That was messed up.
I have so far not migrated towards the new go modules. I am beginning the
process. Looking for ideas.
I split my applications into independent packages each in its own directory.
the structure might look like:
top/src
/pkg1
/pkg2
the imports are based on relative paths - eg:
import (
"../pkg1"
)
Questions:
- there is just 1 go.mod at the top level right?
- go.mod only specifies what the external packages are.
eg.google.olang.org/package
this appears a bit counter to the go module setup.
what are the recommendations regarding internal packages.
appreciate pointers.
thanks, srini
On Monday, January 27, 2020 at 6:29:04 PM UTC-5, R Srinivasan wrote:
>
> I have so far not migrated towards the new go modules. I am beginning the
> process. Looking for ideas.
>
> I split my applications into indepe
>
--
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/6f6ef65f-8fea-45d5-80ac-c50732ce48b3%40googlegroups.com.
