duanjiani6826 2019-07-26 03:08
浏览 46
已采纳

为什么此版本标签会导致错误?

In my go.mod file, I have:

require (
    // ... editted for brevity
    github.com/Liquid-Labs/catalyst-firewrap v2.0.0-prototype.3
    // ... 
)

When I tried to build another package dependent on this package, I get: invalid module: github.com/Liquid-Labs/catalyst-firewrap should be v0 or v1, not v2 (v2.0.0-prototype.3).

There was a rewrite back before go went modular, and I wasn't tagging stuff back then, so there is no v1... is that the problem? I'm not having any luck finding an explanation of the underlying problem here.

  • 写回答

1条回答 默认 最新

  • dtoqemais553654797 2019-07-26 03:54
    关注

    Per the Go modules wiki:

    If the module is version v2 or higher, the major version of the module must be included as a /vN at the end of the module paths used in go.mod files (e.g., module github.com/my/mod/v2, require github.com/my/mod/v2 v2.0.0) and in the package import path (e.g., import "github.com/my/mod/v2/mypkg").

    The same document quotes the rationale from the official Go FAQ:

    Packages intended for public use should try to maintain backwards compatibility as they evolve. The Go 1 compatibility guidelines are a good reference here: don't remove exported names, encourage tagged composite literals, and so on. If different functionality is required, add a new name instead of changing an old one. If a complete break is required, create a new package with a new import path.

    and:

    If an old package and a new package have the same import path, the new package must be backwards compatible with the old package.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 jupyterthemes 设置完毕后没有效果
  • ¥15 matlab图像高斯低通滤波
  • ¥15 针对曲面部件的制孔路径规划,大家有什么思路吗
  • ¥15 钢筋实图交点识别,机器视觉代码
  • ¥15 如何在Linux系统中,但是在window系统上idea里面可以正常运行?(相关搜索:jar包)
  • ¥50 400g qsfp 光模块iphy方案
  • ¥15 两块ADC0804用proteus仿真时,出现异常
  • ¥15 关于风控系统,如何去选择
  • ¥15 这款软件是什么?需要能满足我的需求
  • ¥15 SpringSecurityOauth2登陆前后request不一致