Interesting. Thanks, I'll give it a try.
On Thu, Nov 19, 2020 at 7:08 PM 'Dan Kortschak' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> You should tag the version with the path to the module root: for
> example path/from/root/v1.2.3
>
> On Thu, 2020-11-
Hi,
I've recently encountered an interesting behavior of go modules.
I have a library in a repository on github. The go.mod file for this
library is not in the root directory of the repo. I create a signed tag in
the repo, say v1.2.3.
However when I try referring the full path to the module in t
Hi,
Are there any tools that would allow to manage licenses of my go modules?
I would like to be able to specify what licenses of my dependencies are
allowed.
Are there any plans to add something like this to standard go tools?
Thanks,
Victor.
--
You received this message because you are subs