KDevelop 2.1.5 release with KDE 3.1

Ralf Nolden nolden at kde.org
Tue Jan 21 12:32:05 UTC 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Dienstag, 21. Januar 2003 11:50, falk.brettschneider at gmx.de wrote:
> Hi Ralf!
>
> I recommend to make sure that the whole branch still compiles and works
> well with KDE-2.2 respectively KDE-3.0, too. Can you promise this? Noone
> but you is still testing the KDE_2_2_BRANCH...
>
> I would turn to a tr("Wildsau"), if this stable and finished branch was
> messed up for those versions. ;-) Nobody wants to repair things there
> again.

Yes, I used #ifdef's for KDE versions. The whole stuff was a mere qt3 issue 
and still works with KDE 2.2 because the #ifdef's contain the changes and 
they only apply for KDE 3.x/Qt 3.x.  KDE 2.2 systems aren't affected by the 
update anyway.

Ralf
>
> Ciao
> F at lk
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi,
> >
> > I'd like to inform you that with the help of Dirk Schmitt and Stephan
> > Kulow
> > I've merged a patch that was originally for SuSE to use the
> > doxygen-generated
> > KDE-libs apidocs with kdevelop 2.1 into the KDE_2_2_BRANCH version and
> > fixed
> > up the missing parts so that it works correct and nicely now. I also
> > fixed a
> > problem with jumping to the error location in the output window that
> > seems to
> > be occuring with Qt 3.1 since the output window derives from
> > QMultiLineEdit
> > which is deprecated but still there and derives from QTextEdit.
> >
> > This together with the fact that the KDE 3.1 kde-i18n packages won't ship
> > the
> > kdevelop translation files any more to enable users to upgrade to a
> > KDevelop
> > 3 on KDE 3.1 systems without breaking their kde-i18n packages into
> > conflicts
> > but to still enable users to use KDevelop 2.1 on their KDE 3.1 system in
> > their native language and have issues fixed, KDE will release a KDevelop
> > upgrade as KDevelop 2.1.5 for KDE 3.1 together with that release.
> >
> > In case you upgrade from KDE 3.0 to KDE 3.1 please use your vendor's
> > packages
> > for KDevelop 2.1.5 which is recommended to be used on KDE 3.1.
> >
> > Can someone update the KDevelop website, please when the announcement for
> > KDE
> > 3.1 is out ?
> >
> > Thanks,
> >
> > Ralf
> > - --
> > We're not a company, we just produce better code at less costs.
> > - --------------------------------------------------------------------
> > Ralf Nolden
> > nolden at kde.org
> >
> > The K Desktop Environment       The KDevelop Project
> > http://www.kde.org              http://www.kdevelop.org
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.1 (GNU/Linux)
> >
> > iD8DBQE+LQbTu0nKi+w1Ky8RAmXkAKCV43cDcNZg8ak2fqJ212GiBtEQdwCfdTd5
> > 3hBf/HghO1vYZzwxlUZKqwU=
> > =MShs
> > -----END PGP SIGNATURE-----
> >
> >
> >
> > _______________________________________________
> > Kdevelop-devel mailing list
> > Kdevelop-devel at barney.cs.uni-potsdam.de
> > http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

- -- 
We're not a company, we just produce better code at less costs.
- --------------------------------------------------------------------
Ralf Nolden
nolden at kde.org

The K Desktop Environment       The KDevelop Project
http://www.kde.org              http://www.kdevelop.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+LS6du0nKi+w1Ky8RAr+sAJ4t0iRgBWETEGUi4JggLR92r+lOMACeMnlD
L6Toxm+8b6B6Zop3Z7ZI2tA=
=qW0S
-----END PGP SIGNATURE-----






More information about the KDevelop-devel mailing list