Binary compatibility broken? between 3.3.1 and 3.3.2

[Willy De la Court]

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


is there a problem with binary compatibility please read completely

On Wednesday 01 December 2004 20:17, Rex Dieter wrote:
> Willy De la Court wrote:
> > On Wednesday 01 December 2004 18:59, Rex Dieter wrote:
> >>Willy De la Court wrote:
> >>>system RH9 repo's stable testing unstable
> >>>
> >>>[wdl at wormhole wdl]$ akregator
> >>>akregator: relocation error: akregator: undefined symbol:
> >>>_ZN11KMainWindow7setIconERK7QPixmap
> >>>[wdl at wormhole wdl]$ rpm -q akregator
> >>>akregator-1.0-0.fdr.1.beta8.rh90
> >>
> >>WORKSFORME.  Anyone else?  Might want to verify you are fully current,
> >>at least qt/kdelibs-wise.
> >
> > I think i found it
> >
> > KMainWindow.setIcon was introduced in kde 3.3.2 and is not present in
> > 3.3.1 see the webcvs
> >
> > http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/kdeui/kmainwindow.h?sort
> >by=date
> >
> > the version 1.114.2.2 which is tagged KDE_3_3_1_RELEASE has no setIcon
> > and version 1.114.2.3 tagged KDE_3_3_2_RELEASE has the setIcon function
> >
> >
> > hmm strange if i recall correctly this breaks binary compatibility
>
> You caught me.  It's true.  I built these recent packages against
> kde-3.3.2 (due to be released real-soon-now).  Bummer that
> bin-compatibility was broken.
>
> Is it worth filing a bug?  Dunno if they'll even consider it a bug.
> Qt/KDE has always maintained forward compat (stuff built on/for qt/kde
> 3.x.y will/should work with qt/kde 3.x.(y+1) ) but not necessarily
> vice-versa.
>


- -- 
Simple things make people happy.
Willy De la Court
PGP Public Key at http://www.linux-lovers.be/download/public_key.asc
PGP Key fingerprint = 784E E18F 7F85 9C7C AC1A D5FB FE08 686C 37C7 A689
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFBrhxI/ghobDfHpokRAis2AJ4sZW0ZkOreMbDby9w7tFEHnuMNJgCg61nX
8UEPS7CczKbZde/KGF9esfE=
=l+DZ
-----END PGP SIGNATURE-----