aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorKatharina Fey <kookie@spacekookie.de>2019-10-05 22:42:42 +0000
committerKatharina Fey <kookie@spacekookie.de>2019-10-05 22:44:50 +0000
commit73d865b1dae7585d0eff167271dabe77c9d0b8e6 (patch)
tree337324fab29014f3d60a8bff4979e397fb556d88 /README
parent670a2de0037acadb83433165344710dd3ac03adf (diff)
parente14d8e29606feddb29d7c27ea62dd514ef80f1e4 (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 'README')
-rw-r--r--README23
1 files changed, 23 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
index 00000000000..0ffae5f5ec9
--- /dev/null
+++ b/README
@@ -0,0 +1,23 @@
+LIBKOOKIE
+=========
+
+This is my personal collection of nix expressions. It replaces my old
+`kookiepkgs` [0] and `nixcfg` [1] repositories. It contains a subtree
+of nixpkgs, overlays and modules.
+
+`overlays/patches`: patches to upstream packages
+`overlays/pkgs`: custom out-of-nixpkgs packages
+`nixpkgs`: subtree of nixpkgs (follows unstable)
+`modules`: system configuration modules
+`roots`: available entry-points (machines)
+`ext`: possible private extensions
+
+The `activate` script can be used to switch to a new system
+configuration
+
+
+
+---
+
+[0]: https://git.sr.ht/~spacekookie/kookiepkgs
+[1]: https://git.sr.ht/~spacekookie/nixcfg