tree aa97f9ef2032e0df14007aa4b385591dda3673d0
parent 5f06994f1a6b97fa8bfef9b85f820ccf6082b7de
author Cameron Martin <cameronmartin123@gmail.com> 1712311087 +0100
committer GitHub <noreply@github.com> 1712311087 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJmD8s/CRC1aQ7uu5UhlAAAQUUQABFf4xFoOyRCt2DY5GWgTOKm
 oW+86ye+GT2Adtz9rtgmI0HU9TxuBvzJDUh8Iti3Qw4f5rWYoi0vc5LpPVdYNo1M
 hqB2vUVea+RsT/RqgbHMPPSplF4pLPrjCtE1Jfx+fV2MVD1ENCKYEB0zLJElaypq
 FKNdjz1XRpiKEmrWI0SWx4RrXpmsV2UqRRj4Nvm/Nv5XHL63mbw2l8VXAE9mExp9
 IhkuDnw0qRcyuoEOGC6UvsRZAf1v0Ua4udXksL/18gcbCSoHUXBPKFCyJtGFn/Zq
 edggiimfiRiTYzMxIDDhmhVx38EYrrUoFD1esJExq0JPXH+LGqprbX2/e9VVnYFk
 28gUwPodybooMQUq44N2NIX/HG5pHhzDFFloE6GTl4dFtYmDeKogIMC/TRvK370s
 W7EwZ0lbxKIZvldc2unq0lDVwX3hm/j9C8uiah10m1I/clweXoyKoxN5As8UNllO
 BnVjUgEOlcWn9rYFjX3hj/LIsM5g/tkt5bkrZMMJMcBXhddgck6AOBoBgFghiWHl
 qvUdK8xz3W4kW0SOAaFUnd93N5VAlmKovPBMI4qFE7eH2VriVjs2k+CpNOOKBwyX
 XKj92om/vxeyxiFNfeFQ/CZia1IsV819J6jhE3jn4RsvQ3YKibbIaeoNhWN6VBWK
 FlVwFSAt/NhsJUdDSukW
 =JNeH
 -----END PGP SIGNATURE-----
 

Make bazel lock file cross-platform (#2453)

Since the host tools are os and arch specific, previously bazel would
cache the resolution of these in the lock file, causing the repo for the
wrong OS or arch to be used when moving between machines.

Since bazel 7.1.0, module extensions can be marked as reproducible to
exclude these from the lock file. However, the `rust` module extension
handles fetching of all the other toolchains as well as the host tools,
and we don't really want to exclude those too. Therefore the host tools
are moved to their own module extension. This means we can no longer
match the host toolchain's version, edition, etc with the toolchain
registered via `rust.toolchain` by default, and instead default to a
fixed version. This can still be overridden separately in the root
module. I think this is okay, because the host tools are only used for
bootstrapping and I don't think there's much need to have them match.

This is tested by now checking in the MODULE.bazel.lock file of the
bzlmod example, and running the bzlmod examples on multiple platforms
with `--lockfile_mode` set to `error`.

Resolves #2452
Resolves #2549