Skip to content

fix(toolchain): no chmod on windows when downloading hermetic toolchain #2693

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

Merged
merged 1 commit into from
Mar 23, 2025

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Mar 23, 2025

Previously the code would not chmod for the Windows hermetic toolchains
because there is usually no need - Windows does not have chmod and if
you are downloading the Windows repo on a UNIX system, you won't run it,
so it will stay as is.

However, that left a single case where somebody may want to download the
Linux toolchain on a Windows and the main cases are:

  • bazel sync
  • build a docker image on Windows using rules_oci or similar.

Fixes #2660

Previously the code would not chmod for the Windows hermetic toolchains
because there is usually no need - Windows does not have chmod and
if you are downloading the Windows repo on a UNIX system, you won't
run it, so it will stay as is.

However, that left a single case where somebody may want to download
the Linux toolchain on a Windows and the main cases are:
* `bazel sync`
* build a docker image on Windows using `rules_oci` or similar.

Fixes bazel-contrib#2660
@aignas aignas requested a review from rickeylev as a code owner March 23, 2025 10:08
@rickeylev rickeylev added this pull request to the merge queue Mar 23, 2025
Merged via the queue into bazel-contrib:main with commit 1299307 Mar 23, 2025
3 checks passed
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.

python_register_toolchains breaks bazel sync on Windows
2 participants