Moving pop, imap and smtp koslaves from kdebase to kdepim
Ingo Klöcker
kloecker at kde.org
Thu Jan 8 01:20:53 GMT 2004
On Wednesday 07 January 2004 18:05, Thiago Macieira wrote:
> Bo Thorsen wrote:
> >On Wednesday 07 January 2004 03:39, Thiago Macieira wrote:
> >> I don't suppose the PIM developers counted on having to maintain
> >> binary and behaviour compatibility with the ioslaves as they will
> >> be released in KDE 3.2, have they?
> >
> >No need for this - you don't link directly to a slave. Just like you
> > don't need to maintain binary compatibility for an executable for
> > the shell to be able to start it.
>
> Agreed. Drop the binary compatibility issue. But the question remains
> for behaviour compatibility.
Of course the slaves will be behavior compatible. The KDE 3.2 slaves are
all behavior compatible with all KDE 3 applications (written for KDE
3.0, 3.1 and 3.2). This won't change with the separate release. What
makes you think that we would violate binary and/or behavior
compatibility?
Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040108/f81bdcd4/attachment.sig>
More information about the kde-core-devel
mailing list