Closed mmorel-35 closed 3 months ago
Hi, Matthieu! Thanks for being the kind of person who tries to leave things better than you found them. Could I ask you to help me understand the underlying issue here? What are we trying to solve for by making the repo name different? (My best understanding is that it's some kind of migration setting for folks that want to change names?)
Hey, Matthieu! As in the other PR, would it work for your use case to use this tool as it's designed as a dev dependency?
That is
bazel_dep(name = "hedron_compile_commands", dev_dependency = True)
from the readme, rather than
`bazel_dep(
name = "hedron_compile_commands",
version = "",
)
in your hessian2 PR.
(This tool is normally used directly as s dev dependency to make code editing and listing more ergonomic, and not brought in transitively. If you're using it for some other purpose, just lmk!)
I created https://github.com/bazelbuild/bazel-central-registry/pull/1989/files
This makes the module name and repo_name distinct