KCalendarSystem-related API changes (Re: Compiling Koffice)
faure at kde.org
Mon Jan 13 11:26:35 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Saturday 11 January 2003 17:46, Pupeno wrote:
> I'm running KDE HEAD, but there are two things I want stable in my KDE, KMail
> and KOffice.
> That's why I tried to compile KOffice 1.2.0 and 1.2.1, neither of them
> compiling leading to various compiling erros, not even kspread compiled.
This is due to the introduction of KCalendarSystem in kdelibs-cvs-head.
Hans: the removal of public methods is source-incompatible - yes, removing
- -DKDE_NO_COMPAT fixes it, but we can't fix already released code,
like KOffice-1.2.1 (and the thousand of apps on apps.kde.com, etc. ...)
This means people downloading koffice-1.2.1 and trying to use it with kdelibs-CVS
or KDE-3.2 (which will surely happen a lot if there's no new version of koffice by then!),
can't compile it.
KDE_NO_COMPAT is about kde-3.0 stuff: it means "my app is clean as far as
the kde-3.0 API is concerned, I don't use any kde-2 stuff that has been deprecated".
This is why so many apps have that flag enabled. But you changed the meaning into
"my app is clean wrt the kde-3.2 API", which can't be true for all the
existing released apps! Such a thing can only be done for a new major release
anyway. KDE-3.2 _must_ be source compatible with KDE-3.1 !
You want to warn _developers_ => use kdWarning() in those deprecated methods.
Going for compilation breakages creates trouble for users (who compile from
sources), not only for developers, so it's not appropriate.
Please consider readding the deprecated methods as public, adding kdWarning
into them to warn people about them.
David FAURE, faure at kde.org, dfaure at klaralvdalens-datakonsult.se
Contributing to: http://www.konqueror.org/, http://www.koffice.org/
KOffice-1.2.1 is available - http://download.kde.org/stable/koffice-1.2.1/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the kde-core-devel