6 ms·

The even healthier choice is to store all your system state in a config, you can then just occasionally clean up the config. This also lets you put extensive co

The even healthier choice is to store all your system state in a config, you can then just occasionally clean up the config. This also lets you put extensive comments on why a package is needed or even create a submodule for a specific project. Shame that the only bistro that lets you do this is extremely arcane and difficult to learn if you do not have a PhD in mathematics.

pxc 2y ago
> Shame that the only distro that lets you do this is extremely arcane and difficult to learn if you do not have a PhD in mathematics. Hey, there are two! Remember GuixSD
- anthk 2y ago
  Guix is not that difficult.
  - pxc 2y ago
    I don't think NixOS is either, but I figured I'd let a shitposter have their hyperbole. :) I don't begrudge any Guix contributors protesting that the GuixSD docs are undersold by such hyperbole, though! If that's you, carry on. :D
curt15 2y ago
Is the mapping from config -> state reproducible? Traditional distros drift over time with lots of upgrades because the state is not just a pure function of the set of packages to be installed (the "config"). It could depend on the system's history, such what packages were installed or removed in the past. The so-called "atomic" distros don't attempt to make the (config -> state) transformation reproducible but rather sidestep the problem by snapshotting and replicating the output of the transformation -- the files on disk after various installs, upgrades, and config changes.