forked from extern/nix-config
05100eca7e
Looking back at this, meta packages should be one of the most convenient ways to keep track of packages. It gets the job done and should be more than sufficient for our use case. In particular, installing all packages guarantees that we won't "miss something" and have to install it manually, which is more useful than having a lower package number count. The main disadvantage is dealing with constant updates to large packages in a restrictive internet environment, although it's possible to mitigate this by separating the smaller packages from the larger ones. |
||
---|---|---|
.. | ||
color-scripts | ||
sensible-chromium | ||
tari-core | ||
README.md |
PKGBUILDs
I use PKGBUILDs to know exactly what I have on my machine, and to make it easy to sync changes across multiple Arch installations.
Note that you can install multiple DEs and WMs at once, then switch between them with your display manager (although the practicality of this is questionable).
Packages
- color-scripts - Color scripts, purely for aesthetics
- tari-core - Meta package for my Arch Linux installation