| Summary: | KDE-free build dependencies | ||
|---|---|---|---|
| Product: | [Applications] Falkon | Reporter: | speps <speps> |
| Component: | general | Assignee: | David Rosca <nowrep> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
speps
2018-05-10 10:50:05 UTC
Just remove "po" directory if you don't want translations, and then it won't look for KI18n. Also KI18n is Tier 1 Framework (only depends on Qt), so I see no problem here. It is just a matter of depending on one more library, it doesn't pull all KDE Frameworks. (In reply to David Rosca from comment #1) > Just remove "po" directory if you don't want translations, and then it won't > look for KI18n. As I already mentioned, actually all the translations (but the hellokitty one) are in the ./poqm folder, so they got processed right by cmake, installed and working without ki18n. Why hellokitty belongs to "po" and why it could not be part of "poqm"? > Also KI18n is Tier 1 Framework (only depends on Qt), so I see no problem > here. It is just a matter of depending on one more library, it doesn't pull > all KDE Frameworks. Surely. KI18n does not depend on the KDE framework libraries, but it is still part of it. I agree with your point, my only big concern here is if this would be the first step of a gradually Falkon strong integration into KDE and a relative conversion into a no more DE agnostic browser. I hope this is not the case. Thanks for your work. |