-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove pre-Go 1.17 build tags #5525
Conversation
edab573
to
963e4d3
Compare
Is there a validation preventing this from coming back in future updates? What is the typical behavior in vscode etc. or how is it controlled there? |
Sorry, no idea, I don't use VSCode. I use GoLand. It highlights these tags as obsolete and suggests removing them. |
|
963e4d3
to
2a01b48
Compare
Is there an actual problem with tags still being added? Or they are just legacy leftovers? If you really want, I can add a job similar to opencontainers/runc#4332 |
If we want smth like this it would not be a new ci job but embedded in our sandbox like any other validation tool we are using. |
I should add that the I do recall that when I removed them in moby (using |
Looks like go fix left a couple behind here as well; git grep '// +build' -- ':!vendor/'
examples/gobuild/main.go:// +build ignore
tools/tools.go:// +build tools
worker/runc/runc.go:// +build linux
worker/runc/runc_test.go:// +build linux |
Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
2a01b48
to
0a5a80c
Compare
I'd prefer to leave this out of scope of current PR.
Fixed |
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.
LGTM (non-binding)
I believe that BuildKit cannot be built with such an old Go and there's no reason to keep these legacy tags.
The only manual change is
util/archutil/generate.go
. All the rest is just a result ofgo fix ./...