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. |
||
|---|---|---|
| .. | ||
| install-scripts | ||
| PKGBUILDs | ||
| screenshots | ||
| bootstrap.sh | ||
| Makefile | ||
| README.md | ||
Tari - My Arch Linux setup
Arch Linux, a GNU/Linux distribution, lets you build your own environment. Since you only install what you want, it is easy to customize and control.
Features
- A universal color scheme consistent across all terminal software
- A universal theme across both Qt and GTK applications
- Full HiDPI support for Qt, GTK, and X-level software applications
- Easily switch between both traditional and HiDPI resolution in the same X environment
Usage
On a fresh Arch install, run ./bootstrap.sh.