You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
build: vendor blst as a subtree or equivalent shared source #8144
The system-library CI build currently needs blst even though blst is not provided by the supported Linux distributions. As a result, contrib/containers/ci/ci.Dockerfile repeats the blst source version, checksum, and build configuration already maintained in depends/packages/blst.mk.
Keeping those values in two places allows the CI image and depends build to silently use different blst revisions or build options when one pin is updated without the other. The duplication was introduced by #8106, which builds linux64_asan against system libraries.
Proposed direction
Move blst into a git subtree, or use an equivalent repository-owned source layout, so that the source and relevant build configuration have a single versioned owner. Update both the depends build and the system-library CI image to consume that source without maintaining independent pins.
The implementation should also account for:
preserving the required blst patches and build flags for each supported configuration;
retaining reproducible, reviewable updates to the vendored blst source;
keeping licensing and upstream provenance clear; and
removing the duplicated Dockerfile pinning once the shared source is in place.
This is a follow-up to the dependency-drift concern raised in the #8106 review. The current CI change can proceed with the duplicated pin; this issue tracks eliminating that long-term maintenance hazard.
Activity