This is best shown with a reproducible example.
From within the Bazel source code, this works.
build --//tools/build_defs/pkg:incompatible_no_build_defs_pkg
From a different repository (for example, one where we want to run CI with all incompatible flags set), //tools/build_defs does not exist, so we have to refer to it via the repository name bazel exports:
build --@bazel_tools//tools/build_defs/pkg:incompatible_no_build_defs_pkg
Alas, that does not parse, either in bazel sources or in other repositories.
The severity of the issue is that owners of rule sets are unable to make an incompatible flag change that their downstream users can test.
This is best shown with a reproducible example.
From within the Bazel source code, this works.
build --//tools/build_defs/pkg:incompatible_no_build_defs_pkgFrom a different repository (for example, one where we want to run CI with all incompatible flags set), //tools/build_defs does not exist, so we have to refer to it via the repository name bazel exports:
build --@bazel_tools//tools/build_defs/pkg:incompatible_no_build_defs_pkgAlas, that does not parse, either in bazel sources or in other repositories.
The severity of the issue is that owners of rule sets are unable to make an incompatible flag change that their downstream users can test.