wdisplays VS kde

arandr replacement: wdisplays

Output/display configuration tool: kanshi, wdisplays, wlr-randr

... because I like quick, and lazy: https://github.com/cyclopsian/wdisplays

My approach to managing Plasma keywords is by pulling in the KDE overlay. The kde overlay manages keywords files that can be symlinked into your own package.accept_keywords directory.

That doesn't matter. What /u/Gualdrapo is talking about are the files contained in Documentation/package.accept_keywords which you can symlink into /etc/portage/package.accept_keywords to accept "unstable" versions of Plasma without having to manage the list of packages yourself.

If you are interested in having the latest plasma, you might consider pulling in the kde overlay. Within that overly there is a "Documentation" directory with automatically generated packages.accept_keywords files that you can use to accept ~amd64 for entire categories of KDE (this is what I'm talking about here. Create a symlink to those files in /etc/portage/package.accept_keywords, and then you shouldn't have issues.

My preferred GUI environment is KDE Plasma, and I like having the newest version available asap, and I imagine on most of my systems, Plasma makes up the majority of my keywords. If I managed those keywords directly, I might be in your same position, but I take advantage of the package.accept_keywords files available from the kde overlay to unmask the appropriate version of kde-plasma/kde-frameworks/kde-apps. This means all I'm doing is updating a symlink when kde plasma 5.23 comes out. for example.

The kde overlay is useful from that perspective in the sense that they have pre-made keywords files in their Documentation directory that you can link to in your /etc/portage/package.accept_keywords instead of having to manually keyword the individual packages yourself. Makes things a lot easier. This is the directory I'm talking about on the kde overlay on their git mirror.