Closed alexzorin closed 4 years ago
I think the list can be significantly further purged by excluding the examples (cmd/
) from the main module.
The Go modules wiki page (https://github.com/golang/go/wiki/Modules) calls this out:
Two example scenarios where it can make sense to have more than one go.mod in a repository:
if you have usage examples where the examples themselves have a complex set of dependencies (e.g., perhaps you have a small package but include an example of using your package with kubernetes). In that case, it can make sense for your repository to have an examples or _examples directory with its own go.mod, such as shown here.
Thanks, the examples folder with its own go.mod make sense to me and at this point I would also migrate the CLI under examples.
Do you want to provide a PR for those changes?
Thanks
As a developer, I initially ended up writing my own godbus code because this library pulled too many dependencies.
However, I noticed that quite a few of the deps here don't seem to be used at all. Running
go mod tidy
on master produces the below change.It would bring the footprint down quite a bit. The rest of the library looks great, thank you for implementing the DBus APIs.