Re: wip/acme-dns

[Benny Siegert <bsiegert%gmail.com@localhost>]

> It does seem like a ridiculous number of modules, but I think somewhat
> go is like that, trying keeping up with node.
>
> Reading the list, I see it starts:
>
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.26.0.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.34.0.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.38.0.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.44.1.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.44.2.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.45.1.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.46.3.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.50.0.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.52.0.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.53.0.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.54.0.mod
>   GO_MODULE_FILES+=       cloud.google.com/go/@v/v0.54.0.zip

The .mod files are merely metadata and are just a few hundred bytes at
most. A full "version" is the .mod and corresponding .zip file.

The go tool has an unfortunate behavior: if you update, say, the
cloud.google.com/go module to a newer version, it will keep the
checksum to the *old* .mod file in go.sum, which means that our infra
will add this to GO_MODULE_FILES. If you removed the extra .mod files
from the Makefile, the build would complain. If you also remove the
files from go.sum, the build would go fine. So they are used in some
way, though I am not sure which.

I believe there is a command (go mod tidy?) that removes these
extraneous entries from go.mod. I am not suggesting that we do this on
some upstream release however.


-- 
Benny