Hopefully the pending work will make it for the upcoming release. The plan is to get this stabilised as soon as possible.
Created attachment 899361 [details, diff] disable documentation viewer For the benefit of anyone else who finds this issue and wonders about installing kdevelop on systems where qtwebengine can not be installed (ppc64le) this patch can be dropped in to /etc/portage/patches/dev-util/kdevelop and it will disable the documentation viewer so that kdevelop will compile. To satisfy the ebuild dependencies you can add dev-qt/qtwebengine-5.15.14 to /etc/portage/profile/package.provided
The benefit would be even greater if you'd submitted this upstream (in upstreamable form of course) so we could make this available as USE flag eventually.
I would like to inform the upstream developers at the URL associated with this issue that yes, I do use KDevelop on non-x86, non-arm platforms and have for years, but it's impossible to create an account over there to comment because every attempt is flagged as spam.
I'm not sure where you want to comment. You've got a patch, so you can create an MR. If you are talking about the "Issues" section in gitlab (invent.kde.org), this is *not* for user support or bug reports. There's bugs.kde.org for that.
Did the search on bugs.kde.org for you. You can reference this upstream bug when you've produced an upstreamable patch to submit as MR.
Last but not least, just some indication they would be open to patches. Please note that all development happens on git master first, so don't bother with Qt5-based branches at this point.
(In reply to Andreas Sturmlechner from comment #4) > I'm not sure where you want to comment. You've got a patch, so you can > create an MR. On MR 522 there was a comment: "What are you planning to run it on that isn't x86_64 and aarch64? or is it theoretically for linux distros that build for every platform?" The developer doesn't know he has users on other architectures so normally I'd comment to let him know. I would be willing to make an upstream MR with my change but I can't create an account on their Gitlab. KDE Gitlab links to https://identity.kde.org for account creation and that site says "Client rejected by anti-spam identification measures".
(In reply to Justus Ranvier from comment #7) > On MR 522 there was a comment: "What are you planning to run it on that > isn't x86_64 and aarch64? or is it theoretically for linux distros that > build for every platform?" > > The developer doesn't know he has users on other architectures so normally > I'd comment to let him know. Okay. I've found that, and the answers are not really negative. But this was a high volume KF6 porting tracker, not the right place to opt for unrelated changes. > I would be willing to make an upstream MR with my change but I can't create > an account on their Gitlab. KDE Gitlab links to https://identity.kde.org for > account creation and that site says "Client rejected by anti-spam > identification measures". So first of all, your change needs to have a proper cmake build switch with webengine support default enabled. Then, please contact KDE sysadmins e.g. via #kde-sysadmin on IRC or Matrix so they can look into your problem regarding the account creation.
(In reply to Andreas Sturmlechner from comment #8) > So first of all, your change needs to have a proper cmake build switch with > webengine support default enabled. If course if I made a real upstream MR I'd clean it up substantially. What I posted in this thread is just a quick and dirty "make it work" patch in case anyone else finds it useful.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/kde.git/commit/?id=860dd1d3762b2a734fd6634969de4c82bd629d09 commit 860dd1d3762b2a734fd6634969de4c82bd629d09 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2024-08-22 19:54:07 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2024-08-22 20:03:10 +0000 dev-util/kdevelop: unkeyword 24.08.0 for ~x86 dev-qt/qtwebengine:6 is not keyworded there. Bug: https://bugs.gentoo.org/925719 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> dev-util/kdevelop/kdevelop-24.08.0.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a40d0b19c3e018e024e5e351fb3d028b864d7871 commit a40d0b19c3e018e024e5e351fb3d028b864d7871 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2024-08-31 11:28:45 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2024-09-02 07:17:38 +0000 dev-util/kdevelop: drop 24.05.2 Closes: https://bugs.gentoo.org/925719 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> dev-util/kdevelop/Manifest | 1 - dev-util/kdevelop/kdevelop-24.05.2.ebuild | 130 ------------------------------ dev-util/kdevelop/metadata.xml | 2 +- 3 files changed, 1 insertion(+), 132 deletions(-)
(In reply to Justus Ranvier from comment #9) > (In reply to Andreas Sturmlechner from comment #8) > > So first of all, your change needs to have a proper cmake build switch with > > webengine support default enabled. > > If course if I made a real upstream MR I'd clean it up substantially. Are you still planning to do that, or do you already have an upstreamable patch meanwhile, but only failed at upstream account creation (as mentioned above)?
