[Kde-pim] Kolab usage of kdepimlibs, kdepimlibs split

[David Jarvie]

On Mon, June 25, 2012 9:13 am, Volker Krause wrote:
> On Saturday 23 June 2012 14:36:20 Kevin Ottens wrote:
>> On Saturday 23 June 2012 02:17:58 Christian Mollekopf wrote:
>> > On Friday 22 June 2012 17.28:14 Sune Vuorela wrote:
>> > > On 2012-06-22, Christian Mollekopf <mollekopf at kolabsys.com> wrote:
>> > > > The preferred way forward is pulling those libraries out of
>> > > > kdepimlibs,
>> > > > along the lines of what is happending for frameworks, with only
>> > > > the dependencies which are really required.

>> > We certainly need some solution before frameworks though (kimap &
>> > kcalcore are most pressing currently).
>
> the libraries in pimlibs are already fairly stand-alone, your problem will
> be the kdelibs dependencies and the stuff pulled in that way I think.
>
>> > Maybe it would be possible to already do the split in a branch, which
>> can
>> > depend on a reasonably low kdelibs (4.3), in a way that the result of
>> > that can then actually be used when kdepimlibs is ready for a split.
>
> The most important stuff used from kdelibs are KTcpSocket (imap) and
> KDateTime
> (kcal) I think, for none of which you want outdated versions (if they are
> available in 4.3 at all). To make this work on a 4.3 kdelibs I'd expect
> you
> end up shipping copies of those and by-pass the ones from kdelibs, which
> is very painful and in no way reusable for the version 5 frameworks work.

Also note that KSystemTimeZones, which KDateTime uses, currently relies on
the KDED module ktimezoned to monitor the current system time zone. You'd
have to consider whether to keep that dependency or if not, what to do
instead.

-- 
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/