Office/ and Utilities/ menu reorganization
Christoph Cullmann
cullmann at babylon2k.de
Tue Aug 9 09:40:52 BST 2005
On Tuesday 09 August 2005 02:10, Michael Nottebrock wrote:
> On Tuesday, 9. August 2005 02:02, Michael Nottebrock wrote:
> > On Tuesday, 9. August 2005 01:02, Christoph Cullmann wrote:
> > > For small apps, that is most stressful, small apps will perhaps only need
> > > few lines changes per kdelibs/qt release to keep the user happy (e.g. to
> > > fix regressions with the new versions, to adopt to some little new stuff,
> > > to fix bugs), than you have to made a tarball, notifiy the translators if
> > > a string change was done, ....
> >
> > I don't buy any of that. Qt and Kdelibs are binary compatible
>
> and source compatible, too, of course :)
That's all nice and true, but normally, you have some workarounds in your app for some stuff missing atm,
if a new release of qt/kde comes up and have the proper stuff inside, you fix that workaround, and tada, you have depency
on new kde/qt lib, you must repackage, ... And that perhaps only for a 2 lines change to do things right. Same is true for stuff
Thiago has said about buggy parts, you have workarounds for misbehaviour, new parts have this fixed, the workarounds won't work
now or even harm the app, you have to fix, hu, new deps, new package. That are only some cases, could think of more, like you hide
parts of the gui of a part, it gets more actions, you need to hide more manually, you need to fix (yes, apps do such stuff, therefor I get killed
if I add senseless actions to katepart each minor release). There are lots of such deps and hassles not covered by: oh, we are source and even
binary compatible.
cu
Christoph
--
Christoph Cullmann
KDE Developer, kde.org Maintainance Team
http://www.babylon2k.de, cullmann at kde.org
More information about the kde-core-devel
mailing list