| Summary: | Hard dependency on KGAPI should be optional | ||
|---|---|---|---|
| Product: | [Applications] kmailtransport | Reporter: | Luke-Jr <luke-jr+kdebugs> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | montel |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Luke-Jr
2018-10-15 11:49:07 UTC
The messageviewer in KMail requires QtWebEngine anyway. Do you have a usecase for using kmailtransport outside of KDEPIM applications? My end goal is to use KDEPIM without QtWebEngine. Your end goal probably would be QtWebEngine support for your platform. I very much doubt KDEPIM will revert the work of the recent years to go back to the (long unmaintained) QtWebKit, but I let KDEPIM developers decide what to do with this ticket. Even when QtWebEngine is ported, I don't intend to install/use it. Javascript is a security hazard. Same goes for QtWebKit. (In reply to Luke-Jr from comment #2) > My end goal is to use KDEPIM without QtWebEngine. it will never arrive. Sorry. And "kmailtransport 18.08.2 seems to have added a hard dependency on KGAPI " it has a phabricator review and Dan and me told that we don't want it in source. After that you can patch for your distro but for sure we will not do it in official source. Regards. Upstream Chromium seems to have major security issues every month. QtWebEngine gets updated far less frequently, and often goes months or longer vulnerable to easily exploited issues. Won't you reconsider, please? (In reply to Luke-Jr from comment #6) > > Won't you reconsider, please? No, unless Qt supports another web engine, this won't change. |