6ca65d02eb
Since I figured out how to run both KDE and GTK applications with their proper settings under any lightweight window manager, and since I now know how to configure these programs independent of their desktop environments, this commit removes plasma-desktop, with the possibility of gnome-shell bring removed in a future commit as well. The rationale is that using a desktop environment is counter-intuitive when you already use a window manager. Having multiple desktop environments to start a session with is certainly amusing, but not at all practical, especially when you can accomplish anything that needs to be done with any window manager. Switching between GNOME, Plasma, and bspwm also caused some inconsistent X settings that I assume are non-trivial to fix without a proper restart of the X server. Simply starting the Plasma desktop environment will create quite a few files in ~/.config. These files consist of window coordinates and other non-friendly things, which, IMO, should not belong in the *user's* config directory. Regarding other software, GNOME MPV is arguably easier to use and less buggy than baka-mplayer. Manipulating archives is also much easier with file-roller than it is with ark. Since I got Audacity to look decent on a HiDPI display, I no longer have a use for Kwave, which did not have some of the essential features I used in Audacity anyway. l3afpad functions much more like a notepad than kwrite, which is what I'm looking for since I already use Vim. Using Cantata as a mpd client is simply not the same as using ncmpcpp. zathura and evince are more than enough for document viewing, hence the removal of Okular. |
||
|---|---|---|
| .. | ||
| bspwm-round-corners-git | ||
| color-scripts | ||
| tari-core | ||
| xeventbind | ||
| 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...