If -qtwebengine is set as a USE flag for kde-apps/kdenetwork-meta, it should either depend on kio-gdrive[-kaccounts] or simply not depend on kio-gdrive at all as kde-apps/kaccounts-providers requires net-libs/signon-ui which in turn requires dev-qt/qtnetengine and the expected result of setting -qtwebengine for a KDE meta package is that merging said package does not pull in qtwebengine
This bug is still an issue for me. Despite having disabled qtwebengine globally (i.e. the USE flag "-webengine" in make.conf) in order to avoid installing dev-qt/qtwebengine in my two Gentoo Linux installations (amd64 and ~amd64), I still have to create an edited version of the kde-apps/kdenetwork-meta ebuild in my local overlay in order to remove the hard dependency on kde-misc/kio-gdrive, as discussed in the following threads in the forums: https://forums.gentoo.org/viewtopic-t-1131627.html https://forums.gentoo.org/viewtopic-t-1133043.html
No one needs to edit an ebuild when they can set kio-gdrive[-kaccounts].
(In reply to Andreas Sturmlechner from comment #2) > No one needs to edit an ebuild when they can set kio-gdrive[-kaccounts]. OK, understood. I also found I had to change USE flag "+share" to "-share": # rm /usr/local/portage/kde-apps/kdenetwork-meta/* # echo "kde-misc/kio-gdrive -kaccounts" > /etc/portage/package.use/kio-gdrive # emerge -1v kio-gdrive These are the packages that would be merged, in order: Calculating dependencies / !!! Problem resolving dependencies for kde-misc/kio-gdrive ... done! !!! The ebuild selected to satisfy "kio-gdrive" has unmet requirements. - kde-misc/kio-gdrive-21.12.3::gentoo USE="handbook share -debug -kaccounts -test" ABI_X86="(64)" The following REQUIRED_USE flag constraints are unsatisfied: share? ( kaccounts ) # echo "kde-misc/kio-gdrive -kaccounts -share" > /etc/portage/package.use/kio-gdrive # emerge -1v kio-gdrive These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] acct-group/mail-0-r1::gentoo 0 KiB [ebuild N ] kde-frameworks/kcalendarcore-5.92.0:5/5.92::gentoo USE="-debug -doc -test" 257 KiB [ebuild N ] acct-user/mail-0-r1::gentoo 0 KiB [ebuild N ] acct-user/postmaster-0-r1::gentoo 0 KiB [ebuild N ] net-mail/mailbase-1.8::gentoo USE="pam" 0 KiB [ebuild N ] dev-libs/cyrus-sasl-2.1.28-r2:2::gentoo USE="gdbm pam ssl -authdaemond -berkdb -kerberos -ldapdb -mysql -openldap -postgres -sample (-selinux) -sqlite -srp -static-libs -urandom" ABI_X86="32 (64) (-x32)" 3,946 KiB [ebuild N ] kde-apps/libkgapi-21.12.3:5::gentoo USE="nls -debug -test" 240 KiB [ebuild N ] kde-misc/kio-gdrive-21.12.3:5::gentoo USE="handbook -debug -kaccounts -share -test" 70 KiB Total: 8 packages (8 new), Size of downloads: 4,511 KiB [...] # emerge -1v kdenetwork-meta These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] kde-apps/kdenetwork-meta-21.12.3:5::gentoo [21.12.3:5::local_overlay] USE="bittorrent -dropbox -samba -webengine" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB >>> Verifying ebuild manifests >>> Emerging (1 of 1) kde-apps/kdenetwork-meta-21.12.3::gentoo >>> Installing (1 of 1) kde-apps/kdenetwork-meta-21.12.3::gentoo >>> Jobs: 1 of 1 complete Load avg: 1.46, 3.07, 2.55 >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. I assume ufeindschiff's bug report (Comment #0) is still applicable, though, given the existing RDEPEND in the kde-apps/kdenetwork-meta ebuild?: # grep kio-gdrive /usr/portage/kde-apps/kdenetwork-meta/kdenetwork-meta-21.12.3.ebuild >=kde-misc/kio-gdrive-${PV}:${SLOT} Additionally, given that I also had to set "-share" as a USE flag in order to get kde-misc/kio-gdrive to build, if "-qtwebengine" is set as a USE flag for kde-apps/kdenetwork-meta then should it depend on kde-misc/kio-gdrive[-kaccounts -share] (or, alternatively, not depend on kde-misc/kio-gdrive at all)?
So first and foremost, this bug is still open because of the acknowledgement that the situation is less than ideal. - meta ebuilds are here to provide what people expect to be a "full" experience - lacking kio-gdrive in that sense would be perceived to be a bug when (indirect) qtwebengine usage is actually optional in that package itself I see two ways out of this: 1) Establish how useful kio-gdrive actually is without "-kaccounts -share" and if it isn't, scrap those flags entirely (to justify it being moved to kdenetwork-meta[-webengine] or turn it into a default enabled "+webengine" flag. (altough the latter would be ugly) 2) Nag kdenetwork-meta[-webengine] users with a kio-gdrive[-kaccounts,-share] USEdep chain conflict by default (could be deemed an acceptable byproduct for users trying to go minimal) which *will* cause bugs because people struggle to interpret Portage output too often
As far as I can see, when the USE flags "-webengine", "-kaccounts" and "-share" are set there is no entry for Google Drive in System Settings. Would you expect there to be an entry? If there is no entry, is kio-gdrive redundant? I don't use Google Drive, so to be forced to have kde-misc/kio-gdrive installed seems to me to be wasteful and unintuitive. At least the kde-apps/kdenetwork-meta ebuild in my local overlay with the dependency on kde-misc/kio-gdrive removed didn't force me to have kde-misc/kio-gdrive installed.
(In reply to Fitzcarraldo from comment #5) > As far as I can see, when the USE flags "-webengine", "-kaccounts" and > "-share" are set there is no entry for Google Drive in System Settings. > Would you expect there to be an entry? If there is no entry, is kio-gdrive > redundant? Obviously not, because then it would not be using the kaccounts system but a qtkeychain backend. (In reply to Fitzcarraldo from comment #5) > I don't use Google Drive, so to be forced to have > kde-misc/kio-gdrive installed seems to me to be wasteful and unintuitive. At > least the kde-apps/kdenetwork-meta ebuild in my local overlay with the > dependency on kde-misc/kio-gdrive removed didn't force me to have > kde-misc/kio-gdrive installed. This argument by users of -meta ebuilds on its own has always been futile. By the same logic we would have people requesting a kdegames-meta flag for kmahjongg etc. because they are only playing knights. So don't come back at me with the "wastefulness" argument when using a meta ebuild is not something you use if you pick and choose your applications in the first place.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/kde.git/commit/?id=1613a8504d2ccaff9df3916b07ef8988b9353f92 commit 1613a8504d2ccaff9df3916b07ef8988b9353f92 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2022-07-21 10:10:30 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2022-07-21 10:19:30 +0000 kde-apps/kdenetwork-meta: Update IUSE webengine, re-add IUSE telepathy - Switch back IUSE webengine->telepathy - With the flag by default disabled we can allow it to diverge from our IUSE=webengine revdep "rule", similar to kde-apps-meta[pim]. - Also, stop enforcing a minimum ${PV} for plasma-telepathy-meta in anticipation of us stopping to package future zombie releases of it altogether. - Move kde-misc/kio-gdrive behind IUSE +webengine Due to the package dropping its IUSE=kaccounts option we can now move it behind the established anti-qtwebengine flag. Bug: https://bugs.gentoo.org/782505 Bug: https://bugs.gentoo.org/859544 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> kde-apps/kdenetwork-meta/kdenetwork-meta-22.07.80.ebuild | 6 +++--- kde-apps/kdenetwork-meta/kdenetwork-meta-22.08.49.9999.ebuild | 6 +++--- kde-apps/kdenetwork-meta/kdenetwork-meta-9999.ebuild | 6 +++--- kde-apps/kdenetwork-meta/metadata.xml | 3 ++- 4 files changed, 11 insertions(+), 10 deletions(-) https://gitweb.gentoo.org/proj/kde.git/commit/?id=288a8bb2abb705f4477a4643f2fc742fcaeeb2f4 commit 288a8bb2abb705f4477a4643f2fc742fcaeeb2f4 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2022-07-21 09:59:08 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2022-07-21 09:59:08 +0000 kde-misc/kio-gdrive: Drop IUSE=kaccounts Google Account authentication is currently broken at runtime without kaccounts integration, and qtkeychain backend code is getting increasingly crusty with build broken in >=22.07.80 as well. Reported upstream and option disabled until fixed there. This gets rid of REQUIRED_USE and makes this logically sound to be hidden behind IUSE=webengine within kdenetwork-meta because of kde-apps/kaccounts-providers hard-depending on dev-qt/qtwebengine. KDE-bug: https://bugs.kde.org/show_bug.cgi?id=439639 KDE-bug: https://bugs.kde.org/show_bug.cgi?id=456975 Bug: https://bugs.gentoo.org/782505 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> kde-misc/kio-gdrive/kio-gdrive-22.07.80.ebuild | 12 ++++-------- kde-misc/kio-gdrive/kio-gdrive-22.08.49.9999.ebuild | 12 ++++-------- kde-misc/kio-gdrive/kio-gdrive-9999.ebuild | 12 ++++-------- kde-misc/kio-gdrive/metadata.xml | 1 - 4 files changed, 12 insertions(+), 25 deletions(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1c7d07f251d178f8eb288843ef69437732f1cb30 commit 1c7d07f251d178f8eb288843ef69437732f1cb30 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2022-07-21 10:10:30 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2022-07-21 10:34:32 +0000 kde-apps/kdenetwork-meta: Update IUSE webengine, re-add IUSE telepathy - Switch back IUSE webengine->telepathy - With the flag by default disabled we can allow it to diverge from our IUSE=webengine revdep "rule", similar to kde-apps-meta[pim]. - Also, stop enforcing a minimum ${PV} for plasma-telepathy-meta in anticipation of us stopping to package future zombie releases of it altogether. - Move kde-misc/kio-gdrive behind IUSE +webengine Due to the package dropping its IUSE=kaccounts option we can now move it behind the established anti-qtwebengine flag. Closes: https://bugs.gentoo.org/782505 Closes: https://bugs.gentoo.org/859544 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> ...ork-meta-22.04.3-r1.ebuild => kdenetwork-meta-22.04.3-r2.ebuild} | 6 +++--- kde-apps/kdenetwork-meta/metadata.xml | 3 ++- 2 files changed, 5 insertions(+), 4 deletions(-) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f20e29ce68aae40c5532f23fa97fdeb512289535 commit f20e29ce68aae40c5532f23fa97fdeb512289535 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2022-07-21 09:59:08 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2022-07-21 10:34:32 +0000 kde-misc/kio-gdrive: Drop IUSE=kaccounts Google Account authentication is currently broken at runtime without kaccounts integration, and qtkeychain backend code is getting increasingly crusty with build broken in >=22.07.80 as well. Reported upstream and option disabled until fixed there. This gets rid of REQUIRED_USE and makes this logically sound to be hidden behind IUSE=webengine within kdenetwork-meta because of kde-apps/kaccounts-providers hard-depending on dev-qt/qtwebengine. KDE-bug: https://bugs.kde.org/show_bug.cgi?id=439639 KDE-bug: https://bugs.kde.org/show_bug.cgi?id=456975 Bug: https://bugs.gentoo.org/782505 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> ...io-gdrive-22.04.3.ebuild => kio-gdrive-22.04.3-r1.ebuild} | 12 ++++-------- kde-misc/kio-gdrive/metadata.xml | 1 - 2 files changed, 4 insertions(+), 9 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1760bced65bfdbb88a1bb0a758135a8a65104c01 commit 1760bced65bfdbb88a1bb0a758135a8a65104c01 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2022-07-21 10:29:42 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2022-07-21 10:34:27 +0000 profiles: amd64/x32: Mask kde-misc/kio-gdrive Bug: https://bugs.gentoo.org/782505 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> profiles/arch/amd64/x32/package.mask | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
