[Kroupware] Re: [PATCH] Fixes Bug 49802: vcard does not get displayed, kmail shows error instead

[Cornelius Schumacher]

On Thursday 28 November 2002 07:47, Don Sanders wrote:
> KMail and its dependent kdenetwork libraries need to be moved into
> kdepim. Those dependent libraries are mimelib and libkdenetwork (the
> later could do with a renaming). Other kdenetwork apps that also rely
> on these libraries should be moved into kdepim also.

In how much code would this result? What would be the size of kdepim after 
moving KMail, its dependencies and the apps that depend on that? How would 
this compare to other KDE CVS modules?

> This is because kdepim should be able to make independent releases,
> like KOffice, and the users should be able to get all there pim apps
> from one package.

Distributions tend to split up the CVS modules for making packages. So what 
the user gets isn't necessarily defined by the structure of the CVS.

About independent releases: I don't think it's a good idea to make independent 
releases of kdepim like KOffice does. We should take part in the normal 
release cycle, otherwise we would need a significant amount of additional 
work to organize the releases which I think is better spent on coding.

This does not mean that it wouldn't make sense to make additional releases of 
parts of kdepim independently of the standard KDE release plan. For example 
we could release KitchenSync before 3.2, if it shows to be usable.

> Moving the KMail Part interface into kdelibs isn't a good solution, as
> it means pim users will end up having to update kdelibs to update
> kdepim, and that means they will end up having to update all of KDE.

As a developer you can update parts of kdelibs and you will have to anyway 
because libkabc is in kdelibs. Making a separate release of parts of kdelibs 
is certainly also possible, although it will require some additional effort.

At the moment there is nothing like a KMail specific KPart interface, so we 
maybe should postpone the discussion about that until we have one.

-- 
Cornelius Schumacher <schumacher@kde.org>