tree bf70cc0aeb5e64337619e9c0b3434bc424a9edfd
parent d88c8d5d4b7c458b3c0f894ad46700aa4fca7b39
author Xùdōng Yáng <wyverald@gmail.com> 1636037792 +1100
committer GitHub <noreply@github.com> 1636037792 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhg/SgCRBK7hj4Ov3rIwAADTMIAFTuvBfUzHP0awe6ntMJa9My
 kRb2gEfOEQ8zohO77UoRvFpxL0Uqz8USf1IdSb6Nk1VfIcQBz+V16ayFwYSgZCwq
 y3nPEuwG5pT0vKkCxiPjPyeSAAkV+JrmssQM79PmbrqY9bH8BUnbM70QvrREH9iN
 kIYGMfo4mOaME0UkzvjvjrmOTZNmrI4MKSYc+K3Evta3b/nnUYdUr00LRCyJoxHd
 12iNhaWeFeO+6UIU7LkS1TEaHOi+Z2W++213qfU65JYy0E775DosLb0yVP6slAEu
 EkNqH6ohv63pIMMvyqDgnJDIsKfkEzdgsbDzLGj1shUV0Zhj//YF8yYjHvrIVuA=
 =YkBA
 -----END PGP SIGNATURE-----
 

Use repo-relative labels wherever possible (#9187)

* Use repo-relative labels wherever possible

The label `@com_google_protobuf//:foo` within the protobuf repo is often synonymous with just `//:foo`. We should prefer the latter as it allows us to use a shorter name for the module in the Bazel Central Registry (so just "protobuf" instead of "com_google_protobuf").

Note that the semantics can be subtle: in a macro, plain strings are anchored to the *calling* repo, so if we just use `//:foo` as the default value of a macro argument, it will be resolved to `@myrepo//:foo` if the macro is called from the repo `@myrepo`. In this case, it's necessary to directly call the `Label()` constructor to anchor the string label to the repo where the .bzl file lives.

See https://github.com/bazelbuild/bazel-central-registry/pull/28#issuecomment-954741081 for a bit more context.

* fix protobuf_deps.bzl