kdepim depends on kdenetwork through mimelib

Marc Mutz mutz at kde.org
Tue Sep 3 12:10:47 BST 2002

Hash: SHA1

On Tuesday 03 September 2002 03:41, Don Sanders wrote:
> I agree with marc that mimelib does not belong in kdelibs. But there
> is a clear and consistent need for kde-pim and knode/kmail to share a
> library. We either need to put all these applications in the same
> package or make a new library package that kde-pim and kdenetwork
> depend on.
> I actually tend to think moving KMail and KNode into a package with
> kde-pim makes the best sense. Pity we don't have a better name than
> kde-pim, kde-groupware might be better.

We talked about that with Cornelius and Danimo recently. The consensus
seemed to be that we keep the packages sepearate until integration
requires merging.

This Exchange plugin now makes all this moot, I guess.

Still, I think that the current status quo should be kept at least until
3.1 is out of the door.

If you are working on an IMAP server, why do you need mimelib? You can 
just fetch only the body-part you are interested in. To find out, which 
one that is, use the BODYSTRUCTURE fetch command, which tells you the 
mimetypes of every bodypart (except the encrypted ones, but for that 
mimelib won't help you either).

At worst, you have to undo the CTE, but I think that the server/IMAP 
slave combination does that for you if you only fetch a body part. If 
not, there are numerous implementations of base64 and qp available: 
KCodecs in kdecore and KMime::Codec in kdenetwork (scheduled to be 
moved to kdelibs for 3.2).


- --
They [RIAA,MPAA] are trying to invent a new crime:
interference with a business model.
                           --Bruce Schneier, Crypto-Gram 08/2002
Version: GnuPG v1.0.7 (GNU/Linux)


More information about the kde-core-devel mailing list