Closed johanbrandhorst closed 4 years ago
I would also ask if we can retire 1.10.x
and 1.11.x
? These releases are no longer supported by the official go project, since the release of 1.13.x
.
Those requirements are only for the cmd
. Can the go.mod
file be moved there?
I'd NACK. Please see: https://github.com/varlink/go/issues/11#issuecomment-536488389
Those requirements are only for the
cmd
. Can thego.mod
file be moved there?
I can move the go.mod file to ./cmd
, but it can be a bit of a pain to have several modules per repository (https://github.com/golang/go/wiki/Modules#should-i-have-multiple-modules-in-a-single-repository). Are you sure?
Moved the CLI tool to https://github.com/varlink/go-varlink-cmd .. so the go mod file should not be necessary
As long as the generated files import github.com/varlink/go/varlink
there will be a benefit to using a go.mod file. Are you planning on removing that import path?
Friendly bump.
Fixes #11