On Saturday, January 29, 2011, Christoph Cullmann wrote: > - keep ktexteditor where it is (to have BC+SC kept) and have a small copy > in kate.git to allow easier development (which I will keep in sync with > the REAL on in kdelibs
i can't imagine ever allowing a project that isn't in kdelibs today to do this. as such, i cringe at reading this. it seems extremely fragile and is going to be amazingly confusing to people who may wish to contribute, particularly casually (as i did in a small way last year when i used the KTextEditor interface in plasma-desktop) since you wish to stay with the SC releases, so we don't need to worry about API drift between components due to being outside of a shared release cycle, is there _any_ reason why KTextEditor has to stay in kdelibs? can we just make KTextEditor a dependency for apps that require it and provide a CMake module to find it? -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
