-
Notifications
You must be signed in to change notification settings - Fork 674
[WIP]: build tags #4400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[WIP]: build tags #4400
Conversation
vendor/github.com/containerd/nydus-snapshotter \ | ||
vendor/github.com/containerd/stargz-snapshotter \ | ||
vendor/github.com/containerd/accelerated-container-image | ||
BUILDTAGS=no_ipfs,no_nydus,no_esgz,no_obd make binaries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tags should be named no_${SNAPSHOTTER_NAME}
BUILDTAGS=no_ipfs,no_nydus,no_esgz,no_obd make binaries | |
BUILDTAGS=no_ipfs,no_nydus,no_stargz,no_overlaybd make binaries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
esgz -> stargz - I was wondering - we might want to do that generally (eg: on var and func names as well).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe yes, but it can be discussed separately, as var names and func names are not visible to users and package maintainers.
go mod vendor | ||
rm -rf vendor/github.com/ipfs vendor/github.com/multiformats | ||
BUILDTAGS=no_ipfs make binaries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one should be still tested
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They all are tested below, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, we should still make sure that compilation of no_ipfs
doesn't need explicitly specifying no_stargz
, and vice versa.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see what you mean.
I'll separate them.
Thanks @AkihiroSuda for the early feedback. I will try to get that done tonight before I fly to EU for vacation tomorrow. |
TBD