Skip to content
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

py_proto_library: fix for --legacy_external_runfiles=True #20193

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Feb 1, 2025

py_proto_library: fix for --legacy_external_runfiles=True

Previously, the import path within the runfiles was only correct for the case --legacy_external_runfiles=True (which copied the runfiles into $RUNFILES/<main repo>/external/<external repo>/<path> in addition to $RUNFILES/<external repo>/<path>. This flag was flipped to False in Bazel 8.0.0.

This is identical to the change made to rules_python in bazelbuild/rules_python#2516.

Work towards bazelbuild/rules_python#2581.

@copybara-service copybara-service bot changed the title py_proto_library: external runfiles fix py_proto_library: fix for --legacy_external_runfiles=True Feb 1, 2025
Previously, the import path within the runfiles was only correct for the case `--legacy_external_runfiles=True` (which copied the runfiles into `$RUNFILES/<main repo>/external/<external repo>/<path>` in addition to `$RUNFILES/<external repo>/<path>`. This flag was flipped to False in Bazel 8.0.0.

This is identical to the change made to rules_python in bazelbuild/rules_python#2516.

Work towards bazelbuild/rules_python#2581.

PiperOrigin-RevId: 721941173
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.

1 participant