hercules-ci-{agent,cnix-expr}: Force use of propagated boehmgc #146388
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was already in effect, but only by coincidence. A direct
boehmgc could presumably be added implicitly in the generated
code by fixing the pkg-config to nixpkgs mapping.
This commit should counteract that, or, in case of a rename,
cause an evaluation error so that it can be fixed, instead of
building and crashing at runtime.
Motivation for this change
Make hercules-ci-cnix-expr and hercules-ci-agent packages robust against a potentially disastrous cabal2nix improvement.
bdw-gc = null
in the generated hackage-packages code is technically a bug, but required for nix bindings to work correctly.Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)