Skip to content

Commit 4477823

Browse files
fmeumcopybara-github
authored andcommitted
Use "apparent name" instead of "local name" in Bzlmod docs
"Apparent" is used all over the codebase now, so it makes sense to also use it in user-facing docs. Also slightly rewords the definition of an "apparent repository name" to make it easier to understand. Closes bazelbuild#16548. PiperOrigin-RevId: 484507525 Change-Id: I8e3af88ddbe5f7b31af47d3ea5a6821ac6e71056
1 parent 55f4f48 commit 4477823

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

site/en/build/bzlmod.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -164,9 +164,9 @@ mechanism in the new system. Here are two important concepts:
164164
* For module extension repos: `{{ "<var>" }}module_name{{ "</var>" }}~{{ "<var>" }}version{{ "</var>" }}~{{ "<var>" }}extension_name{{ "</var>" }}~{{ "<var>" }}repo_name{{ "</var>" }}`
165165
<br>(<b>Example</b>. `@rules_cc~0.0.1~cc_configure~local_config_cc`)
166166

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

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

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

0 commit comments

Comments
 (0)