From koffice-devel Tue Mar 23 17:05:19 2010 From: Carlos Licea Date: Tue, 23 Mar 2010 17:05:19 +0000 To: koffice-devel Subject: Re: libkdchart api stability? Message-Id: X-MARC-Message: https://marc.info/?l=koffice-devel&m=126936391903436 On Tuesday 23 March 2010 04:50:25 Johannes Simon escribió: > Though I agree with Thomas, I would argue in a different way. What Carlos > says can really be applied to all software projects out there. No library > that a project depends on is ever 100% bug free, but software developers > have to live with that, otherwise larger modular systems (take any linux > distro for instance) would be a huge mess, each and every software > package shipping their own bug-fixed version of the same library. It is > not any different for KOffice. > > There's exceptions to the rule, e.g. when a library is too unstable, or in > a beta stage, then you use your local copy and apply all bug fixes you > need to make it work for you. But this is not the case with KDChart. It's > been in a stable state for a long time. If you do find a bug, there's > very likely a work-around for it that you can use until the bug-fixed > version has been released. > > Bottom line is, KDChart is not different from other libraries that KOffice > depends on. > > - Johannes Albeit the point you rise is correct, I'm not proposing to include every dependency on KOffice's tree, you're taking my point to the extreme :). In fact, that's so extreme that I've only seen it in one project. All said, I really think that we will complicate our lives by moving KDChart out of KOffice's tree, at least in the short term. A compromise has to be made, I agree with Inge's proposal so that we keep our copy in the repo until, at least, 2.3. That way KDAB has plenty of time to do the KDChart release, and distributions have plenty of time to package it. Carlos Licea _______________________________________________ koffice-devel mailing list koffice-devel@kde.org https://mail.kde.org/mailman/listinfo/koffice-devel