bazel_version rule conflicting with bazelbuild/rules_rust

[tiziano88]

asylo definition of bazel_version:

asylo/asylo/bazel/asylo_deps.bzl

Lines 237 to 243 in 676b9f3

	# Required by gRPC
	if not native.existing_rule("bazel_version"):
	_bazel_version_repository = repository_rule(
	implementation = _bazel_version_repository_impl,
	local = True,
	)
	_bazel_version_repository(name = "bazel_version")

rules_rust definition of bazel_version:
https://github.com/bazelbuild/rules_rust/blob/fe9a91e8b42f731aeb3b596246f6bf4bb9a88dc3/workspace.bzl

This fails compilation with an error similar to:

ERROR: error loading package 'rust/oak_runtime': in /usr/local/google/home/tzn/.cache/bazel/_bazel_tzn/0afd379f1411abdcf552c905c7b0282a/external/io_bazel_rules_rust/rust/rust.bzl: in /usr/local/google/home/tzn/.cache/bazel/_bazel_tzn/0afd379f1411abdcf552c905c7b0282a/external/io_bazel_rules_rust/rust/private/rust.bzl: in /usr/local/google/home/tzn/.cache/bazel/_bazel_tzn/0afd379f1411abdcf552c905c7b0282a/external/io_bazel_rules_rust/rust/private/rustc.bzl: Unable to load file '@bazel_version//:def.bzl': file doesn't exist

since both projects define @bazel_version but with a different internal layout.

Is there a way to disambiguate this in the local WORKSPACE file, or do the two repositories need to agree on a naming convention to avoid the clash?

[tiziano88]

I may have managed to work around this using the very obscure and almost undocumented repo_mapping feature in Bazel: https://docs.bazel.build/versions/master/external.html#shadowing-dependencies

[tiziano88]

Blocks project-oak/oak#313