Recently, kde-plasma/kwin had introduced 'lock' use flag to control the support of kscreenlocker. This is off by default and I appreciate it, as I don't use screen locking. Unfortunately, kde-plasma/plasma-meta does not respect this use flag and it started to force this enabled for kwin, making the flag almost useless (as kwin is primary for Plasma, you don't use kwin with GNOME probably :-)) Please make it the other way round, add the 'lock' use flag also for plasma-meta so that it does not require kde-plasma/kscreenlocker unconditionally and it does not have to force 'lock' enabled for kwin. Reproducible: Always Steps to Reproduce: 1. euse -R lock 2. emerge -avuDN world Actual Results: ... [ebuild U ] kde-plasma/plasma-meta-5.25.5:5::gentoo [5.24.6-r1:5::gentoo] USE="browser-integration crash-handler crypt desktop-portal display-manager elogind handbook kwallet legacy-systray sddm smart wallpapers -accessibility -bluetooth -colord -discover (-firewall) -grub -gtk -networkmanager -plymouth -pulseaudio -sdk -systemd -thunderbolt" 0 KiB Total: 66 packages (63 upgrades, 3 new, 1 uninstall), Size of downloads: 157 052 KiB Conflict: 1 block (all satisfied) The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by kde-plasma/plasma-meta-5.25.5::gentoo # required by @selected # required by @world (argument) >=kde-plasma/kwin-5.25.5 lock Would you like to add these changes to your config files? [Yes/No] Expected Results: ... [ebuild U ] kde-plasma/plasma-meta-5.25.5:5::gentoo [5.24.6-r1:5::gentoo] USE="browser-integration crash-handler crypt desktop-portal display-manager elogind handbook kwallet legacy-systray sddm smart wallpapers -accessibility -bluetooth -colord -discover (-firewall) -grub -gtk -lock -networkmanager -plymouth -pulseaudio -sdk -systemd -thunderbolt" 0 KiB Total: 82 packages (65 upgrades, 3 new, 14 reinstalls, 1 uninstall), Size of downloads: 163 295 KiB Conflict: 1 block (all satisfied) Would you like to merge these packages? [Yes/No]
It doesn't really make sense for plasma-meta since its dependency set brings in kde-plasma/kscreenlocker, inevitably. The IUSE only serves its purpose for users who use kwin as a compositor without using Plasma itself.
(In reply to Andreas Sturmlechner from comment #1) > It doesn't really make sense for plasma-meta since its dependency set brings > in kde-plasma/kscreenlocker, inevitably. why inevitably? if kscreenlocker is dropped from dependencies (conditionally), and kwin can be compiled without it, what else would need it? some systemsettings module? - I hope it could be disabled too ... > The IUSE only serves its purpose > for users who use kwin as a compositor without using Plasma itself. er, I can't find any other package than plasma-meta which would force lock on kwin, so ... "without Plasma" means "without plasma-meta" actually? p.s. while searching, I have found that there are "lock" and "locking" USE flags controlling the same for different packages, probably another RFE material to merge these?
(In reply to kavol from comment #2) > why inevitably? > > if kscreenlocker is dropped from dependencies (conditionally), and kwin can > be compiled without it, what else would need it? some systemsettings module? > - I hope it could be disabled too ... Do you think I haven't done my homework? $ equery d kscreenlocker > kde-plasma/kwin-5.26.0 (lock ? >=kde-plasma/kscreenlocker-5.26.0:5) > kde-plasma/libkworkspace-5.26.0 (>=kde-plasma/kscreenlocker-5.26.0:5) > kde-plasma/plasma-meta-5.26.0 (>=kde-plasma/kscreenlocker-5.26.0:5) > kde-plasma/plasma-workspace-5.26.0 (>=kde-plasma/kscreenlocker-5.26.0:5) So, by any measure of having a 'Plasma' installation you are out of luck of saving that precious kscreenlocker space. (In reply to kavol from comment #2) > er, I can't find any other package than plasma-meta which would force lock > on kwin, so ... "without Plasma" means "without plasma-meta" actually? kde-plasma/plasma-meta is here to ensure that users get a working Plasma installation. What users do with individual Plasma packages is their own matter, no? In fact, my answer to questions about missing 'stuff' will always be: Do you have plasma-meta installed, and if not, check the delta over your set of installed Plasma packages.
