18972fdb81
Since the collective system is known as Tari, having individual parts for the pieces that work together to make the whole is not ideal. Now that I understand more about how Arch Linux works, if I ever needed to create a non-Tari operating system, I would just use pacman to install packages as needed, or modify this PKGBUILD to create a new meta package specific to that system. |
||
|---|---|---|
| .. | ||
| tari-core | ||
| tari-gnome | ||
| tari-plasma | ||
| tari-scripts | ||
| tari-util-xeventbind | ||
| tari-web | ||
| README.md | ||
PKGBUILDs
Here are my PKGBUILDs I use on Arch Linux. Each has a specific use case. I use PKGBUILDs to know exactly what I have on my machine, and to make it easier to sync changes across multiple Arch installations.
Of course, you don't have to use any of these packages for your own installation, but if you want to use my setup, you probably want to use the packages I use as well.
Getting Started
There are some core packages that need to be installed before anything else, listed below:
- tari-core - Core packages I use for many things
- tari-cli - CLI programs that are nice to have
- tari-desktop - Packages I use common to all desktop environments
Add-on packages
Now that everything is installed, it's just a matter of choosing a desktop environment or window manager. Note that you can install multiple DEs and WMs at once, then switch between them with your display manager.
- tari-gnome - The GNOME desktop environment, with GTK-related software
- tari-plasma - The Plasma desktop environment, with Qt and KDE-related software
- tari-bspwm - The bspwm window manager, with optional Qt and GTK support (through
tari-gnomeandtari-plasma)
Other window managers exist, but may not be trivial to use in non-traditional (HiDPI) environments.
Other packages
- tari-scripts - Color scripts, purely for aesthetics
- tari-util-xeventbind - Useful to change X DPI on resolution change
TODO: More to come soon...