nix-starter-configs/minimal/flake.nix
Gabriel Fontes 3face7eddd set overlays through modules
This changes how the templates use nixpkgs. Before, we instantiated
nixpkgs in the flake and passd it directly to the configs; this was good
for consistency, but silently ignored `nixpkgs.*` options, generating
confusion among users. We now use modules to configure nixpkgs.

This should help avoid cases such as:
https://discourse.nixos.org/t/allowunfree-doesnt-work-with-flake-managed-system/21798/17

The drawback is that we can no longer test overlayed packages like so:
`nix build .#foo`, you can do it like so instead: `nix build
.#nixosConfigurations.your-system.pkgs.foo`.

Personally, I've been avoiding override packages globally in my own
config.
2022-11-05 14:43:53 -03:00

42 lines
1.3 KiB
Nix

{
description = "Your new nix config";
inputs = {
# Nixpkgs
nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
# Home manager
home-manager.url = "github:nix-community/home-manager";
home-manager.inputs.nixpkgs.follows = "nixpkgs";
# TODO: Add any other flake you might need
hardware.url = "github:nixos/nixos-hardware";
# Shameless plug: looking for a way to nixify your themes and make
# everything match nicely? Try nix-colors!
# nix-colors.url = "github:misterio77/nix-colors";
};
outputs = { nixpkgs, home-manager, ... }@inputs: {
nixosConfigurations = {
# FIXME replace with your hostname
your-hostname = nixpkgs.lib.nixosSystem {
pkgs = nixpkgs.legacyPackages.x86_64-linux;
specialArgs = { inherit inputs; }; # Pass flake inputs to our config
# > Our main nixos configuration file <
modules = [ ./nixos/configuration.nix ];
};
};
homeConfigurations = {
# FIXME replace with your username@hostname
"your-username@your-hostname" = home-manager.lib.homeManagerConfiguration {
pkgs = nixpkgs.legacyPackages.x86_64-linux;
extraSpecialArgs = { inherit inputs; }; # Pass flake inputs to our config
# > Our main home-manager configuration file <
modules = [ ./home-manager/home.nix ];
};
};
};
}