Moving KMail, KNode, Korn and related libraries to kdepim

Cornelius Schumacher schumacher at
Sat Jan 11 00:07:45 GMT 2003

On Saturday 11 January 2003 01:38, Allan Sandfeld Jensen wrote:
> On Friday 10 January 2003 22:07, Cornelius Schumacher wrote:
> > On Friday 10 January 2003 20:27, Adriaan de Groot wrote:
> > > 3) move shared code to new module and extend the dependency tree
> >
> > It's already hard to handle dependencies inside a module like
> > kdepim. Moving some of the dependencies to something like a
> > kdelibs2 wouldn't make things easier.
> >
> > For me the most appealing argument for moving kmail to kdepim is
> > that this is the option which causes least work to solve our
> > problem of code duplication.
> But it could also clean up kdelibs and kdebase by moving everything
> that requires network-access to kdenetworklibs. Large modules is not
> a solution to anything only a complication and a demodulization.

We are not only talking about network libs. KMail also has hidden 
dependencies on kdepim, so you would end up with a kdenetworkandpimlibs 
module. I can't see how this would make thing less complex than putting 
KMail into kdepim.

Moving KMail to kdepim doesn't mean that we stop to modularize. In fact 
having this in a single module might make it easier to factor out 
common components because there are not so much constraints as in 

Cornelius Schumacher <schumacher at>

More information about the kde-core-devel mailing list