My fourth EngFlow blog post is about using Bazel macros and custom Make variables to access canonical repository names when using Bazel modules. Normally you shouldn’t have to access these names, but these techniques help you do so without depending on the internal canonical repository name format.
Check it out:
This’ll be my last post talking about dealing with canonical repository name related breakages. Next I’ll talk about dealing with WORKSPACE dependencies that themselves aren’t yet Bzlmod ready.
If you’ve any thoughts to share, please comment on the LinkedIn announcement corresponding to this post. I’ve also posted it to #bzlmod channel in the Bazel Slack workspace, in case you’d like to discuss it there. (FWIW, I posted the previous three posts to the #bzlmod channel, too.)