Moving pop, imap and smtp koslaves from kdebase to kdepim

[Thiago Macieira]

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.

Suppose you implement a new protocol-specific command in the new ioslave 
release. Will the IO Master require that command to  be present in 
order to work? If so, this would require an upgrade in the ioslave; if 
not, then users who don't want or can't upgrade (due to monolithic 
packaging of kdebase, for instance) simply will not get new features.

I suppose, however, that would be too much hassle.

-- 
  Thiago Macieira  -  Registered Linux user #65028
   thiagom (AT) mail (dot) com
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- 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/20040107/967827d2/attachment.sig>