Append the workspace name to the runfiles directory name#856
Merged
aiuto merged 1 commit intobazelbuild:mainfrom Apr 24, 2024
Merged
Append the workspace name to the runfiles directory name#856aiuto merged 1 commit intobazelbuild:mainfrom
aiuto merged 1 commit intobazelbuild:mainfrom
Conversation
The runfiles directory is broken down by workspace name. This means that
files belonging to the main workspace are placed at
"${name}.runfiles/${ctx.workspace_name}/${short_path}". Files belonging
to externals have a short_path starting with "../${external_name}".
Because we currently don't append ctx.workspace_name to the computed
runfiles path, files belonging to the main workspace are placed at the
top level of the runfiles directory, which is incorrect. Even worse is
that files belonging to external repositories end up alongside the
runfiles directory, instead of being contained within.
cgrindel
approved these changes
Apr 17, 2024
Collaborator
|
I will wait to merge until @aiuto has had a chance to look at this. |
Collaborator
|
This is probably going to break people, but it is the right thing to do. We're going to have to bump the major version # on the next release. |
This was referenced Apr 24, 2024
|
is this supposed to be released soon? |
Collaborator
|
I can do a release by end of month. |
|
@aiuto sorry for bothering you. |
Collaborator
|
We got a 1.0 release out today. I'm not sure if the BCR update went in.
…On Mon, Jun 3, 2024 at 8:23 AM Ievhenii Korin ***@***.***> wrote:
@aiuto <https://github.com/aiuto> sorry for bothering you.
Are there any updates on release that contains this change?
—
Reply to this email directly, view it on GitHub
<#856 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXHHHC6OSWXOW77MUQFI2TZFRN4FAVCNFSM6AAAAABGLCVTVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGA3DKOBSGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I ran into the issue of Exists, but runfile API returns a bazel module named path The above path The overall setup of the rules: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The runfiles directory is broken down by workspace name. This means that files belonging to the main workspace are placed at "${name}.runfiles/${ctx.workspace_name}/${short_path}". Files belonging to externals have a short_path starting with "../${external_name}".
Because we currently don't append ctx.workspace_name to the computed runfiles path, files belonging to the main workspace are placed at the top level of the runfiles directory, which is incorrect. Even worse is that files belonging to external repositories end up alongside the runfiles directory, instead of being contained within.
This makes the runfiles directory layout consistent with how Bazel creates it locally: