From 742fd8fdd0a66d705def05e2e85522ed1561a813 Mon Sep 17 00:00:00 2001 From: Erik Arvstedt Date: Thu, 19 Oct 2023 09:48:46 +0200 Subject: [PATCH] examples/flake.nix: add `inputs.nixpkgs` To make this template look more like a regular system flake. --- dev/README.md | 1 + examples/flakes/flake.nix | 7 +++++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/dev/README.md b/dev/README.md index 9b93a5c..0e37eb3 100644 --- a/dev/README.md +++ b/dev/README.md @@ -101,4 +101,5 @@ It's easiest to use an existing service as a template: - [flake.nix](../flake.nix): update `nixpkgs.url` - [cirrus.yml](../.cirrus.yml): update toplevel container -> image attribute - [examples/configuration.nix](../examples/configuration.nix): update `system.stateVersion` +- [examples/flakes/flake.nix](../examples/flakes/flake.nix): update `inputs.nix-bitcoin.url` - Treewide: check if any `TODO-EXTERNAL` comments can be resolved diff --git a/examples/flakes/flake.nix b/examples/flakes/flake.nix index 1037a96..355c400 100644 --- a/examples/flakes/flake.nix +++ b/examples/flakes/flake.nix @@ -12,9 +12,12 @@ # You can also use a version branch to track a specific NixOS release # inputs.nix-bitcoin.url = "github:fort-nix/nix-bitcoin/nixos-23.05"; - outputs = { self, nix-bitcoin }: { + inputs.nixpkgs.follows = "nix-bitcoin/nixpkgs"; + inputs.nixpkgs-unstable.follows = "nix-bitcoin/nixpkgs-unstable"; - nixosConfigurations.mynode = nix-bitcoin.inputs.nixpkgs.lib.nixosSystem { + outputs = { self, nixpkgs, nix-bitcoin, ... }: { + + nixosConfigurations.mynode = nixpkgs.lib.nixosSystem { system = "x86_64-linux"; modules = [ nix-bitcoin.nixosModules.default