Conversation
|
Should the build target use -mod=vendor? |
|
ping |
|
ping @ehazlett ^^ |
4e11698 to
4f8fda2
Compare
|
Build succeeded.
|
|
Build succeeded.
|
Signed-off-by: Evan Hazlett <ejhazlett@gmail.com>
|
Build succeeded.
|
Signed-off-by: Evan Hazlett <ejhazlett@gmail.com>
|
Build succeeded.
|
|
@ehazlett How did protobuild fare in this scenario? |
|
@stevvooe I get the following warns: I'm also vendoring everything for backwards compat to help. But since I have them global I think it works. I'm going to try to get this rebased and updated this week to try some more. |
|
@ehazlett some merge conflicts still...? |
|
I'm going to close this one for now since it is not in a reviewable state. My suggestion is that we first update |
As Derek suggested at containerd/containerd#3182, this change adds Go modules support for the script first.
As Derek suggested at containerd/containerd#3182, this change adds Go modules support for the script first. Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
|
containerd/project#25 got merged, can we reopen and get this before 1.3? |
|
I think we could start from the dependencies of containerd such as https://github.com/containerd/go-cni or https://github.com/containerd/continuity. https://github.com/containerd/cri is a bit trickier than others, due to the way Kubernetes manages dependencies. You may need a bunch of |
This adds Go module support.
What I did:
go mod init(imported from vendor)go mod tidyensure indirect importsgo mod vendorvendor copy of all imports for non-module support (pre 1.11, etc)GO111MODULE=on)