nixos/common: forward nix.enable
from the OS configuration
#6383
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.
Description
This prevents problematic references to
nix.package
when Nix management is disabled in the host OS.Drafted until the corresponding
nix.enable
functionality is merged into nix-darwin, since this is probably more useful there than on NixOS.Note: This work was funded by Determinate Systems. The design is my own.
Checklist
Change is backwards compatible. (‐ish; you could theoretically be relying on the host OS’s
nix.package
whennix.enable
is turned off, but that sounds unwise…)Code formatted with
./format
.Code tested through
nix-shell --pure tests -A run.all
or
nix build --reference-lock-file flake.lock ./tests#test-all
using Flakes.Test cases updated/added. See example. (it doesn’t seem like there are any existing tests for
nix.enable
, so not sure where to add this)Commit messages are formatted like
See CONTRIBUTING for more information and recent commit messages for examples.
If this PR adds a new module
Maintainer CC
@rycee