Empty go.mod file in root directory containing only version maps

[Gert]

Example https://github.com/gertcuykens/module/tree/v4.0.0 can I assume it to be good practice to put a empty go.mod file in the root directory that doesn't contain other go files, only the version folders, so the root itself doesn't get recognised as a module itself?

[t hepudds]

Hello Gert,

It looks like you are experimenting with the "major subdirectory" layout for modules.

It looks like your v1 module is incorrectly specified, including with an incorrect trailing "/v1":

   https://github.com/gertcuykens/module/blob/v4.0.0/v1

Usually you would not have a "/v1" subdirectory if you are following the "major subdirectory" layout. If you have the v1 module in the same branch as your v2, v3, and v4 modules, then usually the v1 module would be in the root directory of the repo, and not a /v1 subdirectory, and there would be no traililng "/v1" on the module line of the go.mod there.

This is described in more detail here:

   https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

Note that section also describes an alternative layout called the "major branch" layout for modules, which does not use any "/vN" subdirectories, and which some people find simpler to manage at this point.

There is also a much longer discussion of those two alternative layouts here:

   https://research.swtch.com/vgo-module

 

In summary, I think the answer to your question is "no, that is not a standard practice".

Regards,

thepudds

[Gert]

Thanks, the branch approach makes much more sense https://github.com/gertcuykens/module/tree/v5.0.0