Moving KMail, KNode, Korn and related libraries to kdepim

Allan Sandfeld Jensen kde at
Sat Jan 11 00:38:36 GMT 2003

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.

More information about the kde-core-devel mailing list