A module can consist of multiple packages. The packages in your repository all belong to the module in the root directory of the repo (where your go.,mod file is). And there is nothing wrong with this. You can maintain them all together in the same module.
However, perhaps you want to make one or more packages available for other projects. Then it makes sense to move them into their own module. To use separate modules for your packages, you can do either of these two approaches: Option 1 (preferred). Move your non-main packages into separate repositories. Run go mod init <package path> at the root of each repo to create a module for each package. (Here we have one repo = one package = one module.) Option 2. Keep all packages in your single repo. For each non-main package, cd into the package dir and run go mod init <package path>. Caveat: This way you get nested modules, which is probably not something you really want. See the multi-module repositories FAQ <https://github.com/golang/go/wiki/Modules#faqs--multi-module-repositories> in the Go Wiki.for some reasons against multi-module repos. Plus a cite from Russ Cox: "For all but power users, you probably want to adopt the usual convention that one repo = one module." – Christoph On Saturday, July 25, 2020 at 7:03:44 AM UTC+2 alideve...@gmail.com wrote: > I want to import libraries in module file but modules add all other > libraries except those packages which I had created, DB is one of them. How > to import? > Error <https://github.com/ali2210/WizDwarf/tree/master/db>, please help > me to resolve > > -- 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/a3cdf112-cb4d-4d45-ade8-0b699f4dbe8dn%40googlegroups.com.
