Frameworks/Epics/New Runtime Organization
Appearance
< Frameworks | Epics
kde-runtime reorganization epic
Important Forewords
Runtime requirements of a given Framework will be included in the Framework repository, giving people a "single tarball/repo" solution to use. Even though the runtime and libraries will be housed together, attention should still be paid to ensuring that there is a clean and well engineered split and division between the runtime and libraries. Runtime components that are supposed to be background details should not bleed through the library APIs, libraries should not have build-time dependencies on runtime components, etc.
Runtime Components Planning
Definition of done:
- A component must be migrated to its corresponding Frameworks repository OR be merged into another approriate non-frameworks module (e.g. kde-workspace)
- All i18n and documentation (if any) must be migrated appropriately with it
- Has been cleared by the module maintainer that it is migrated to for inclusion
A spreadsheet was prepared of each component in kde-runtime: https://docs.google.com/spreadsheet/ccc?authkey=CI_3zNMC&key=0Am2uzNh0KAtpdFVaRkMtMXZEcC00MEE0dzhrbWV2Nnc&hl=en_US&authkey=CI_3zNMC#gid=0
Status | Component | Destination | Migrator | Comments | |
---|---|---|---|---|---|
IN PROGRESS | Attica KDE Plugin | ?? | ?? | Dependency on kconfig, port to secret service | {{{5}}} |
IN PROGRESS | kdontchangethehostname | ?? | ?? | merge into kdelibs/kded/kded.cpp (can we get rid of polling?) | {{{5}}} |
IN PROGRESS | khelpcenter� | ?? | ?? | needs a replacement app | {{{5}}} |
IN PROGRESS | kdeui/about� | ?? | ?? | replacement with QML, put into KDE App solution | {{{5}}} |
IN PROGRESS | keditfiletype | ?? | ?? | research replacement | {{{5}}} |
DONE | kactivitymanager | kactivities | Ivan Cukic | {{{5}}} |