| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Add empty WORKSPACE.bzlmod |  Derek Mauro | 2024-01-29 |
| | | | | | | | | | | | | | When bzlmod is enabled and WORKSPACE.bzlmod exists, the content of WORKSPACE is ignored. This prevents bzlmod builds from unintentionally depending on the WORKSPACE file. This exposed some small problems with our clang-cl configuration, which are also fixed in this change. PiperOrigin-RevId: 602511311 Change-Id: I0ba411edde2df0e17f4eeede4117ddb6934dd8f8 | ||
| * | Add support for Bzlmod for the next release | Derek Mauro | 2024-01-11 |
| https://bazel.build/external/overview#bzlmod Bzlmod will be the default in a future Bazel release. By default it requires projects to be registered with the Bazel Central Registry (https://registry.bazel.build/) and thus uses regular releases by default. Users that want to "live-at-head" can still do this through with overrides (https://bazel.build/external/module#overrides). This change updates Abseil dependencies to use released versions. CI uses Bzlmod except in the case of linux_gcc-floor, which will keep testing the old WORKSPACE-based dependency system. PiperOrigin-RevId: 597676666 Change-Id: I8d33facc432477c6dc7daa06fd00bb4ae8c4adba | |||
 |
index : debian-abseil | |
| Debian packaging for Abseil |
| summaryrefslogtreecommitdiff |
path: root/MODULE.bazel