dependencies on KJS/KHTML in kdelibs and kdebase-runtime
sebas at kde.org
Tue Sep 28 13:20:02 BST 2010
On Sunday, September 26, 2010 11:32:00 Rolf Eike Beer wrote:
> koos vriezen wrote:
> > 2010/9/25 Albert Astals Cid <aacid at kde.org>:
> > > May i ask why Kontact Mobile people decided to "patch/fork" kdelibs
> > > instead of working on a solution?
> > Maybe because "patch/fork" kdelibs is a solution to port to mobile
> > (mobile as in pads or handset devices).
> Even if both of you have valid points here I think Albert's point is the
> more future-proof one. So please, everyone that needs to patch kdelibs
> for $whatever reason: please report here why you did it and what you did.
> Maybe people simply were not aware of a problem and would solve it in a
> way that you don't need patching anymore.
That's the platform profiles we've started to implement, they're solving
exactly this problem. So there *is* a sound solution to what was a stop-gap-
measure at first, meaning we have a standard set of features per platform (for
http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
More information about the kde-core-devel