some packages pull in kde4/qt4 packages when use flag kde is set. kde5 should be the default kde now so rename it to kde4 to prevent kde4/kde5 dependency mixture hell. some packages: app-office/libreoffice-5.2.4.2 ww-plugins/adobe-flash-24.0.0.194
media-gfx/darktable[kde]
By that standard, KDE Applications itself is a 'dependency mixture hell' as it contains both kdelibs-4- and kf5-based packages. Yet it is just shipped as upstream intends. When I build libreoffice without USE=kde, then I miss out precious integration into my Plasma-5 environment, no matter that this is done via kdelibs-4. It is the same for packages that use 'kde' as a flag to install kwallet integration - sure it will require kwalletd:4, but that's exactly what I want for a legacy application that I am using in my Plasma-5 environment. Besides the fact that 'kde5' as such does not exist, a flag with that name would be just as misleading as 'kde4', which also does not exist as a coherent software compilation anymore. For the same reason, Plasma profile is still using USE=qt4 by default. We want it for many applications that are not yet ported, for non-KDE applications that only provide an optional Qt4 GUI that continues to work just fine within Plasma-5.
You can still enable kde4 by default in the profile? For those who want legacy functionality. I think apps should be pushed to "upgrade" faster.
I think we should evaluate this on a per-package basis. app-office/libreoffice[kde] provides KDE integration regardless of which KDE environment is used. I think most KDE users would want this, so we should leave as-is. media-gfx/darktable[kde] is for kwallet integration. It appears to happen over dbus, so we should investigate whether kwallet5 can be used as a drop-in replacement. www-plugins/adobe-flash[kde] installs a KDE4-based KCM, and when unset makes a GTK utility available instead. I think we should consider removing this USE flag completely.
+1 for dropping www-plugins/adobe-flash[kde] Not sure about darktable[kde], so far all kwalletd:4 rdeps needed porting to work with kwallet:5...
Let's have a look at optional kwalletd:4 rdeps and flags that they use: kde-apps/kdebase-runtime-meta:4 - oldwallet kde-plasma/kwallet-pam:5 - oldwallet media-gfx/darktable - kde dev-vcs/subversion - kde Then there is kwallet:5 rdeps world: kde-frameworks/kio:5 - kwallet app-crypt/zuluCrypt - kde www-client/qupzilla - kde
With darktable, it may be as easy as adjusting the service and interface names for its kwallet backend to org.kde.kwalletd5.service and kf5_org.kde.KWallet.xml For subversion, USE=kde seems to build more stuff, pulling in Qt4 and kdelibs. Instead, USE=qt4 may not be entirely accurate but would fit comfortably for the request we have here. Also less danger for plasma profile users to lose access except when they wrongly set -qt4. Existing example is plasma-desktop[qt4] that pulls in KDE packages (although to benefit any Qt4 package at runtime). Alternatively, `oldwallet`: Exists within meta packages, but likely no user has it set globally, also the name is a bit dubious on a non-KDE package where it is lacking the context; requires everyone's attention on upgrade.
USE=kde was dropped from www-plugins/adobe-flash. The following packages were switched to USE=kwallet: app-crypt/zuluCrypt dev-vcs/subversion media-gfx/darktable www-client/qupzilla
All packages with USE=kwallet can now alternatively use kde-frameworks/kwallet:5 instead if they still try to talk to the legacy kwalletd4 interface. x11-misc/lightdm[kde] (pulling in x11-misc/lightdm-kde) is on the brink of removal. Can we close this bug?
