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.


    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 控制面板卸载无权限!!
    • ¥20 vb调用dll报错找不到文件
    • ¥20 SQL如何做交集查询
    • ¥15 unity 绘画方面的问题
    • ¥15 FTP 明明给了权限但是还是550 Permission denied问题
    • ¥20 Java的kafka错误unknowHostException
    • ¥20 gbase 8a没有lisense,需要获取一个lisense
    • ¥15 前端的3d饼图不知道用啥框架做的
    • ¥15 算法问题 斐波那契数 解答
    • ¥15 VS2019 SPY++ 获取句柄操作