[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE 4 Core Libraries major features
From:       Cornelius Schumacher <schumacher () kde ! org>
Date:       2006-03-30 18:36:55
Message-ID: 200603302036.55499.schumacher () kde ! org
[Download RAW message or body]

On Thursday 30 March 2006 20:17, Thiago Macieira wrote:
>
> Question #0 is there because I (personally) think that Akonadi doesn't
> belong in the list. So I ask the PIM developers to tell us all again if
> it's supposed to be there. (I'm not denying it's important, I'm
> questioning it's core libs stuff).

Akonadi is replacing libraries which currently are in kdelibs (which I 
consider to be the core libraries) and it provides desktop-wide services 
which should be available to all KDE applications. In the past the policy was 
to not have dependencies between modules. That means that there is no other 
way than putting Akonadi in the core libraries.

Where would you put Akonadi? Will the module structure for KDE 4 be 
significantly different from the current structure?

I would really welcome to have a separate module with all the required 
run-time dependencies for a KDE application (this would be a subset of the 
current kdebase). This would make it much more easy to actually develop for 
KDE 4. At the moment it's a bit hard. If you only compile kdelibs, you are 
missing essential stuff, and compiling kdebase is still a major effort which 
at least for me isn't worth the trouble when working on individual 
applications which aren't in kdebase.

-- 
Cornelius Schumacher <schumacher@kde.org>
[prev in list] [next in list] [prev in thread] [next in thread]