diff options
| author | Katharina Fey <kookie@spacekookie.de> | 2019-10-05 22:42:42 +0000 |
|---|---|---|
| committer | Katharina Fey <kookie@spacekookie.de> | 2019-10-05 22:44:50 +0000 |
| commit | 73d865b1dae7585d0eff167271dabe77c9d0b8e6 (patch) | |
| tree | 337324fab29014f3d60a8bff4979e397fb556d88 /nixpkgs/default.nix | |
| parent | 670a2de0037acadb83433165344710dd3ac03adf (diff) | |
| parent | e14d8e29606feddb29d7c27ea62dd514ef80f1e4 (diff) | |
Replacing nixcfg with libkookierebuild
Generally, nixcfg grew out of a dotfiles repository, that happened to
also have some scripts in it. As more and more of the configuration
was replaced with nix specifics (home-manager, etc...), so did nixcfg
change over time (previously "stuff").
As part of this, kookiepkgs was introduced along-side nixcfg, to make
it easier to add custom things to nixpkgs-based systems
(NixOS). Additionally, the core system configuration was handled via
private infrastructure repositories, each specific to the machine in
question.
The problem with this approach is a lot of redundancy when building
non-userspace (read home-manager) systems and a lot of chaos with
having to cherry-pick commits from different branches to work with
nixpkgs trees in development.
Ultimately, keeping both new package definitions, patches and
configuration for the root system and userspace (home-manager) in the
same repository is a _much_ better approach to solving these issues.
And as such, libkookie was started: the general idea is that it
includes all nix expressions that are relevant to _any_ of my
computers. Under `roots`, a machine can have it's primary
configuration file which is built andcopied into the nix store, so
that nixpkgs can always point at the version a generation was built
with, not what is on disk).
Overlays contains everything that kookiepkgs used to, modules contains
both system-level modules (only required on NixOS), as well as
anything that is being built with home-manager. Modules are all kept
in the same tree, however some require system-level access while
others don't. There could be some kind of list to distinguish the two,
so that userspace-only systems can still take advantage of libkookie.
Diffstat (limited to 'nixpkgs/default.nix')
| -rw-r--r-- | nixpkgs/default.nix | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/nixpkgs/default.nix b/nixpkgs/default.nix new file mode 100644 index 00000000000..a74a01719c7 --- /dev/null +++ b/nixpkgs/default.nix @@ -0,0 +1,28 @@ +let requiredVersion = import ./lib/minver.nix; in + +if ! builtins ? nixVersion || builtins.compareVersions requiredVersion builtins.nixVersion == 1 then + + abort '' + + This version of Nixpkgs requires Nix >= ${requiredVersion}, please upgrade: + + - If you are running NixOS, `nixos-rebuild' can be used to upgrade your system. + + - Alternatively, with Nix > 2.0 `nix upgrade-nix' can be used to imperatively + upgrade Nix. You may use `nix-env --version' to check which version you have. + + - If you installed Nix using the install script (https://nixos.org/nix/install), + it is safe to upgrade by running it again: + + curl https://nixos.org/nix/install | sh + + For more information, please see the NixOS release notes at + https://nixos.org/nixos/manual or locally at + ${toString ./nixos/doc/manual/release-notes}. + + If you need further help, see https://nixos.org/nixos/support.html + '' + +else + + import ./pkgs/top-level/impure.nix |