Kolab2 (www.kolab.org) which is under development has defined a new XML based storage format that allows Kontact, the Kolab2 Webclient and MS Outlook using the Toltec connector. The work for this storage format is contained in a number of proko2 branched files from the KDE_3_3_BRANCH of kdepim. The files that are changed or added is highlighted in the doc/kde-client/cvs-instructions/checkout_proko2.sh file in Kolab CVS. (Also find attached). I propose adding a kolab USE flag to kdepim which will patch kdepim against the proko2 changes and allow a user to exploit the full kolab functionality as it becomes available. Kolab2 is slated for release in November 2004. I am willing to help QA/maintain this change to the kdepim ebuild, although I am not much of a Gentoo developer at the moment. Reproducible: Always Steps to Reproduce: 1. Checkout KDE_3_3_BRANCH for kdepim from KDE CVS Then: cvs up -rproko2 -dP kresources/Makefile.am kresources/kolab cvs up -rproko2 kioslaves/imap4 cvs up -rproko2 kmail/{kmailicalifaceimpl.cpp,kmailicalifaceimpl.h,kmailicalIface.h,kmversion.h} cvs up -rproko2 kmail/{Makefile.am,annotationjobs.cpp,annotationjobs.h,kmfoldercachedimap.cpp,kmfoldercachedimap.h,imapaccountbase.h,imapaccountbase.cpp} cvs up -rproko2 kmail/{kmail.kcfg,configuredialog.cpp,configuredialog_p.h,accountcombobox.cpp,accountcombobox.h} cvs up -rproko2 wizards/{Makefile.am,kolabwizard.cpp,kmailchanges.cpp} cvs up -rproko2 libkdepim/addresseelineedit.cpp cvs up -rproko2 korganizer/{freebusymanager.cpp,version.h,resourceview.cpp,resourceview.h} cvs up -rproko2 libkcal/resourcecalendar.h Actual Results: This will give you the latest version of the Kolab extensions for Kontact. Expected Results: Without these patches full Kolab support will not be possible for Kontact.
Created attachment 38578 [details] Missing files from kdepim (needs to be added for Kolab resources) These files can obtained by running the following agains kdepim CVS: cvs up -rproko2 -dP kresources/Makefile.am kresources/kolab
Created attachment 38579 [details, diff] Kolab2/Proko2 changes against KDE_3_3_BRANCH This patch was created by doing the following: 1) Checkout KDEPIM KDE_3_3_BRANCH 2) Duplicate directory 3) Update one of the checkouts using (part of checkout_proko2.sh in kolab CVS) cvs up -rproko2 kioslaves/imap4 cvs up -rproko2 kmail/{kmailicalifaceimpl.cpp,kmailicalifaceimpl.h,kmailicalIface.h,kmversion.h} cvs up -rproko2 kmail/{Makefile.am,annotationjobs.cpp,annotationjobs.h,kmfoldercachedimap.cpp,kmfoldercachedimap.h,imapaccountbase.h,imapaccountbase.cpp} cvs up -rproko2 kmail/{kmail.kcfg,configuredialog.cpp,configuredialog_p.h,accountcombobox.cpp,accountcombobox.h} cvs up -rproko2 wizards/{Makefile.am,kolabwizard.cpp,kmailchanges.cpp} cvs up -rproko2 libkdepim/addresseelineedit.cpp cvs up -rproko2 korganizer/{freebusymanager.cpp,version.h,resourceview.cpp,resourceview.h} cvs up -rproko2 libkcal/resourcecalendar.h 4)execute diff -u -r kdepim/ proko2/
http://websvn.kde.org/branches/kdepim/proko2/kdepim/ shows at least half of kdepim subdirs are included in the branch... Looks big, and I don't know how stable it's supposed to be, or at what points to take snapshots (and I'm not going to make an svn ebuild...) So we won't be touching this. Even if a dev (or you) wanted to maintain an ebuild for this, the fact that upstream haven't made any releases or even tags tells me it's not stable, so I don't think such an ebuild would enter portage. We'll have to wait for kde 3.5.
Correction, they do have tags and the latest says RC3. If that means there'll be some sort of release (ie before kde 3.5) we can have ebuilds for it, otherwise what I said earlier applies.
