Skip to content

Conversation

@phlax
Copy link
Contributor

@phlax phlax commented Mar 21, 2024

No description provided.

@phlax
Copy link
Contributor Author

phlax commented Mar 21, 2024

this fixes one of the issues mentioned in #386 and makes it easier to run locally

@phlax phlax changed the title ci/buildifier: Install and run with bazel ci/buildifier: Install and run with bazel (+update bazel -> 5.4.0) Mar 21, 2024
Copy link
Member

@PiotrSikora PiotrSikora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This adds the whole Go toolchain as a dependency to projects depending on C++ Host, which doesn't use Go, only to run the buildifier tool as a pre-check, so I'm personally against this change.

Especially, when installing it is a simple:

go install github.com/bazelbuild/buildtools/buildifier@latest

@PiotrSikora
Copy link
Member

This adds the whole Go toolchain as a dependency to projects depending on C++ Host, which doesn't use Go, only to run the buildifier tool as a pre-check, so I'm personally against this change.

...but if you really want, then maybe add this to WORKSPACE and not proxy_cpp_host_dependencies()?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants