WetGeek Then I could check to see how many of those I could replace with equivalent (or better) KDE versions.
@tomscharbach: Upon further research and reflection, I've come to accept that replacing all the GNOME packages with equivalent KDE packages on a Solus system is a plan that's doomed from the start. I created a list of all the installed packages on my laptop and their dependencies, and that list is huge. And it doesn't even take into account reverse dependencies (packages for which the target package is itself a dependency). Nor does it take into account that there may not be a suitable KDE replacement in every case.
As just one example, the more I played unfamiliar KDE versions of the GNOME games that I enjoy, the less I was convinced that it would be easy or appropriate to adopt them instead. The experience just wasn't as enjoyable as I'd hoped it would be, and the advantages of making the switch were not as great as I'd expected.
So I've decided to temper my original enthusiasm for getting rid of all the GNOME applications on my KDE systems. Given Solus' heavy reliance on GNOME, it just isn't as feasible as I'd thought. It took me less than a day to reach that conclusion.
EDIT: I do, however, enthusiastically support your suggestion that the replacement for eopkg and Software Center should identify applications as to KDE-based, GNOME-based. or Independent. A simple (K), (G), or (I) in the display would work well. It would help us to decide which apps we might prefer on which DEs.
