On Sat, 2011-10-15 at 03:35 +0200, Ove Kåven wrote: > Den 13. okt. 2011 17:06, skrev Patrick Ohly: > > Hello Ove! > > > > Just going through older emails... do you need some help with this or > > are the pointers enough? I could provide a untested patch which changes > > the core infrastructure as suggested, as a starting point. > > Sure, that would help... I wasn't sure where to start, and it hasn't > been easy to find time to study how the core engine works - there's a > C++ class jungle in there.
True, this particular change requires some familiarity with how the different pieces work together. I've pushed the necessary changes to the maemo5-recurrences branch, based on current master. It should be possible to cherry-pick this back onto your local Maemo 5 branch: git fetch git cherry-pick origin/master..origin/maemo5-recurrences I renamed the properties and field a bit compared to my original proposal. I'm a bit unhappy about one aspect of the patch: in order to import the additional exdates into the engine, the CalDAV backend has to enable the additional property for import *and* and export. If this workaround works for Maemo, then I'll change it so that the CalDAV backend only passes the additional information to the engine without being asked to store it (which isn't necessary). I verified that the patch series does add EXDATEs as expected by temporarily adding the HAVE-EXDATE-DETACHED to the Evolution calendar backend (not committed). -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
