commit 21cadf4386143421704da9e06ce373c3f31f1444
parent 40311918f548040f47d2fc064ffa03f7ce1fcae6
Author: Vincent Demeester <vincent@sbr.pm>
Date: Sun, 7 Jun 2020 13:27:44 +0200
systems/modules: add git to core
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
Diffstat:
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
@@ -75,7 +75,7 @@ soon-ish 👼):
Most of the `make` commands will try to populate this ahead of time. The assumption is :
have a `sync` folder where the assets are. *Note: how to bootstrap (as syncthing will
not be there, and the `sync` folder either)*
-- `docs`: holds documentation about this code, literate configuration, see [literate configuration](#orgf5cfe83).
+- `docs`: holds documentation about this code, literate configuration, see [literate configuration](#orgb210a13).
`make publish` will publish the `README.org` and the `docs` folder to my website.
- `lib`: shared code used during configuration (mostly `nix` code).
- `machines`: configuration per machines
@@ -85,7 +85,7 @@ soon-ish 👼):
- `private`: holds non-shareable code, like *secrets*.
- `tmp`: things to… organize (e.g. where I import my other *legacy* configuration)
-<a id="orgf5cfe83"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
+<a id="orgb210a13"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
literate configuration files in this repository, I have to think of how to organize files
in order to end up with one huge file. The goal of having those `org-mode` files, is
mainly to document my configuration and publish it, most likely on [sbr.pm](https://sbr.pm).
diff --git a/systems/modules/core/nix.nix b/systems/modules/core/nix.nix
@@ -10,6 +10,7 @@ let
in
{
options = {
+ environment.systemPackages = [ pkgs.git ];
core.nix = {
enable = mkOption { type = types.bool; default = true; description = "Enable core.nix"; };
gcDates = mkOption {
