This is a simple request for convenience, open to discussion. As stated in the summary, I suggest removing the dependencies on kde-base/kdebase-wallpapers. An "equery depends --all-packages kde-base/kdebase-wallpapers" states that currently: • kde-base/kdebase-meta-4.4.5 • kde-base/kdebase-startkde-4.4.5 ... are having a dependency. Before version 4.4.5 kdebase-startkde didn't want to pull in the wallpapers, only kdebase-meta did. I searched a while and couldn't find out *why* these dependencies actually exist. No application relies on those wallpapers, and everything just works fine after manually unmerging the package. The only one which depends on some sort of background image is kde-base/ksplash, which brings its own files along. Back in the days of 3.5 the user could decide if he wanted the extra wallpapers and just merge kde-base/kdeartwork-wallpapers. Today I find it quite annoying to get my own wallpapers cluttered up with that stuff, aside from them being really good pieces of artwork, I simply don't want them getting installed without my explicit wish ;-) Anybody backing up my point? To my understanding, the issue could be solved by simply removing the dependencies off the corresponding ebuilds. If there are strong reasons other than the personal type "KDE devs have fixed to include this stuff", I'd like to hear them explained. Thanks a lot. Reproducible: Always Steps to Reproduce:
those depedencies come from the eclass, and i don't see no reason to remove them for any kdebase-* packages. It will add unnecessary complexity to eclass. kdeartwork is different from kdebase. You can always emerge the wallpapers package with --nodeps (or even just download them from the tarball or from the KDE SVN) if you only want the images.
