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.
Currently, the
cacert
setupHook
, which setsNIX_SSL_CERT_FILE
, triggers for each dependency at$targetOffset
. It does not trigger in cases where there are no such dependencies. When not cross-compiling,cacert
triggers on itself, but, when cross compiling, a dependency at$targetOffset
is often lacking.I propose directly setting
NIX_SSL_CERT_FILE
in thesetupHook
, but perhaps there is a more idiomatic way of implementing this sort of hook.Motivation for this change
To make the
cacert
setupHook
more robust, particularly in the case of cross-compilation.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @