tree 86f268b047f9298ac8918eff74043afb7eebd93b
parent 68acaa5d6aa65e89d99ac775b3d895fea91a3bae
author Ivo List <ilist@google.com> 1597943695 +0200
committer GitHub <noreply@github.com> 1597943695 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfPq+PCRBK7hj4Ov3rIwAAdHIIAKtiGXHaNkL1ILOvswVWrKSl
 EWZecDJfjMTYM9qQJnUZcykQ4uaNw61K6Fnv8qWSIOM9JirRrCYmGSgdTLdA7AtE
 mXgkTXY/+YE12zffyLQDa6xJ/cQqDuPHcWPcCZ8KG7kvFW/fvLnG5/H+6pXN4esy
 mu0ozrJwC6QbnxbXX6WRx1mudOJogDjNZgSSdV9ZXZQ0lkA8y7h6LEu0bZiT/QHk
 L6ZmXLhcvNfzHtrg3ChrQ7Ta6Qxiv7Jl79gIWekxnPPrSeTGzj0yWnzFk3mMTZ6T
 e8qkTT+mn/l8McSh4mMIIrWztTS885ante+vta7EnKDDJClDgo+tHrPUci4nWp8=
 =9gof
 -----END PGP SIGNATURE-----
 

Move bzl ext (#265)

* Move Gazelle extension to //gazelle/bzl and change package name

This fixes an issue with importing bazel-skylib into
google3. Currently, Glaze (internal Go build file generator) attempts
to generate a target (//gazelle:gazelle) that conflicts with one
that's already declared here.

I think the right solution is actually to move the package into a
subdirectory. In the future (bazelbuild/bazel-gazelle#5), Gazelle's Go
extension will generate target names similar to what Glaze does, so
the same conflict will happen in open source. I think it's also
logical to have a directory of packages in case more need to be added
in the future, and for the extension to have a package name matching
the language it works with.

This is an incompatible change, but the //gazelle directory isn't part
of a tagged release yet, so hopefully it won't break anyone.

* fix runfiles access in test

* Fix gazelle package names.

Co-authored-by: Jay Conrod <jayconrod@google.com>