SUMMARY GTK[n] is not installed, so no need to create the config file(s) for it. In this case, gtk2 is not installed, but ~/.gtkrc-2.0 , ~/.gtkrc-2.0-kde4 and ~/.config/gtkrc-2.0 are beieng created. Considering GTK4 is in development and more apps/desktops (xfce,lxde...) are moving or moved already to GTK3, GTK2 will be less relevant but that is another story. Am just requesting to make it optional and/or select which GTK version 2/3/4... a config file will be created. STEPS TO REPRODUCE 1. Well, one would need a "GTK2 free system" 2. 3. OBSERVED RESULT The mentioned config files are created EXPECTED RESULT Create config file(s) only for installed GTK versions. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.1 Qt Version: 5.12.2 ADDITIONAL INFORMATION
Arguably a system without GTK wouldn't have the KCM installed, would it?
(In reply to Aleix Pol from comment #1) > Arguably a system without GTK wouldn't have the KCM installed, would it? It would, but not necessarily GTK2, I have GTK3 installed and am using GTK3 applications. My request, sorry if that wasn't clear, is to create the config files only for GTK versions installed on the system (let's say GTK3 and GTK4). I am hoping for a flexible choice in the KCM, e.g autodetect what GTK versions are installed and offer only those detected in the KCM, or some kind of checkbox/multi choice (don't know the technical term for it), where a user checks the desired GTK version. Or what you see fits.
There's no way of knowing if there's a GTK2 app. It could be in an appimage. And even in the traditional case, we want to cater to the prospect installation of applications. Otherwise the user would need to open the kcm and force write so the kcm could check whether there's gtk2 installed.
(In reply to Aleix Pol from comment #3) If GTK2 is installed then in most cases as a dependency of other app(s), in other words, if there is GTK2, there is also a GTK2 app. My experience with appimage (inkscape), flatpak (libreoffice),.. is that they (apps) tend to use their own theme anyway and ignore user setting (Wayland session). GTK2 here is an example, in future it can be GTK3. I think opening the kcm and applying the changes is "very normal" :-)
(In reply to udevnull from comment #4) > (In reply to Aleix Pol from comment #3) > > If GTK2 is installed then in most cases as a dependency of other app(s), in > other words, if there is GTK2, there is also a GTK2 app. > My experience with appimage (inkscape), flatpak (libreoffice),.. is that > they (apps) tend to use their own theme anyway and ignore user setting > (Wayland session). GTK2 here is an example, in future it can be GTK3. I > think opening the kcm and applying the changes is "very normal" :-) As Aleix mentioned, you could be using an AppImage app that bundles GTK2, so you could be using GTK2 without realizing it and without it being installed via your package manager.
I understand you Nate & Aleix, they dont use system libraries,.. bundle everything. In oder not to "break" stuff in case one uses gtk2/3/.. without knowing it, I would suggest a setting/checkbox by default switched on, so that we are on the safe side and can be unchecked by those who like to disable it. Do you think that is possible/feasible/should I forget it?
I think it's unlikely to be implemented. This level of specificity generally isn't very helpful to most users, and actually becomes an annoyance to most of them. It seems like a lot of potentially fragile code to add for the strong possibility of irritating most of our users. :)