added a comment regarding the use of pkgs.nixos
This commit is contained in:
parent
bc8b37f38d
commit
8d3731eeb3
1 changed files with 9 additions and 0 deletions
|
@ -2,6 +2,15 @@
|
||||||
|
|
||||||
# This automatically searches for nixos configs in ./machines/${name}/configuration.nix
|
# This automatically searches for nixos configs in ./machines/${name}/configuration.nix
|
||||||
# and exposes them as outputs.nixosConfigurations.${name}
|
# and exposes them as outputs.nixosConfigurations.${name}
|
||||||
|
#
|
||||||
|
|
||||||
|
# a comment regarding pkgs.nixos vs lib.nixosSystem
|
||||||
|
# while lib.nixosSystem is the usual enduser way to evaluate nixos configurations
|
||||||
|
# in flakes, pkgs.nixos sets the package set to the packages it comes from.
|
||||||
|
# This spares us tracking our potentiell overlays and own package additions, but just
|
||||||
|
# using the right package set to begin with. Using lib.nixosSystem from the flake we would
|
||||||
|
# need to specify that again.
|
||||||
|
|
||||||
{ withSystem, lib, inputs, ... }: {
|
{ withSystem, lib, inputs, ... }: {
|
||||||
flake = {
|
flake = {
|
||||||
nixosConfigurations = withSystem "x86_64-linux" ({ pkgs, ... }:
|
nixosConfigurations = withSystem "x86_64-linux" ({ pkgs, ... }:
|
||||||
|
|
Loading…
Reference in a new issue