Migrating to Bazel Modules (a.k.a. Bzlmod) - Maintaining Compatibility, Part 2 In the previous post, we reviewed guidelines formaintaining compatibility with both Bzlmod and legacy WORKSPACE builds, andolder and newer dependency versions. I promised that in this post and the next,we'd discuss testing approaches to help ensure that this remains the case. However, a discussion in the Bazel Slack workspace has revealed a Bzlmod andlegacy WORKSPACE compatibilty issue I'd missed in the previous po...| EngFlow Blog
Migrating to Bazel Modules (a.k.a. Bzlmod) - Maintaining Compatibility, Part 1¶| blog.engflow.com
Migrating to Bazel Modules (a.k.a. Bzlmod) - Toolchainization¶| blog.engflow.com
Migrating to Bazel Modules (a.k.a. Bzlmod) - Repo Names, Again…¶| blog.engflow.com
Migrating to Bazel Modules (a.k.a. Bzlmod) - Fixing and Patching Breakages¶| blog.engflow.com
Migrating to Bazel Modules (a.k.a. Bzlmod) - Module Extensions¶| blog.engflow.com
Migrating to Bazel Modules (a.k.a. Bzlmod) - Repo Names, Macros, and Variables The previous two posts in this series showed how to use [runfiles mechanisms][1]and [rules_pkg mechanisms][2] to avoid dealing with canonical repository namesunder Bzlmod. However, one special case remains: when you need to depend on thename of a repository directory, either at build time or runtime. This postexplains how to access canonical repository names in a portable way to solvesuch problems. We'll use a [mac...| EngFlow Blog
Migrating to Bazel Modules (a.k.a. Bzlmod) - Repo Names and rules_pkg¶| blog.engflow.com
Migrating to Bazel Modules (a.k.a. Bzlmod) - Repo Names and Runfiles¶| blog.engflow.com
Migrating to Bazel Modules (a.k.a. Bzlmod) - The Easy Parts¶| blog.engflow.com