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.

Sign up for GitHub

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

Jump to bottom

Use "apparent name" instead of "local name" in Bzlmod docs #16548

Closed
wants to merge 1 commit into from
Closed

Use "apparent name" instead of "local name" in Bzlmod docs #16548

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 5 additions & 5 deletions site/en/build/bzlmod.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,9 +164,9 @@ mechanism in the new system. Here are two important concepts:
* For module extension repos: `{{ "<var>" }}module_name{{ "</var>" }}~{{ "<var>" }}version{{ "</var>" }}~{{ "<var>" }}extension_name{{ "</var>" }}~{{ "<var>" }}repo_name{{ "</var>" }}`
<br>(<b>Example</b>. `@rules_cc~0.0.1~cc_configure~local_config_cc`)

* **Local repository name**: The repository name to be used in the `BUILD` and
`.bzl` files within a repo. The same dependency could have different local
names for different repos.
* **Apparent repository name**: The repository name to be used in the `BUILD` and
`.bzl` files within a repo. The same dependency could have different apparent
names in different repos.
<br>It's determined as follows:

* For Bazel module repos: `{{ "<var>" }}module_name{{ "</var>" }}` by
Expand All @@ -176,10 +176,10 @@ mechanism in the new system. Here are two important concepts:
[`use_repo`](/rules/lib/globals#use_repo).

Every repository has a repository mapping dictionary of its direct dependencies,
which is a map from the local repository name to the canonical repository name.
which is a map from the apparent repository name to the canonical repository name.
We use the repository mapping to resolve the repository name when constructing a
label. Note that, there is no conflict of canonical repository names, and the
usages of local repository names can be discovered by parsing the `MODULE.bazel`
usages of apparent repository names can be discovered by parsing the `MODULE.bazel`
file, therefore conflicts can be easily caught and resolved without affecting
other dependencies.

Expand Down