https://bugs.meego.com/show_bug.cgi?id=14804
Summary: hard-coded rule and code for "supports UID"
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: High
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
Currently the local sync code assumes that both sides have a real, persistent,
creator-assigned UID (as in iCalendar 2.0).
This is not the case for all peers, even those using iCalendar 2.0.
It would be nice if we could use some CtCap extensions which says "yes, I
really support real UIDs" in contrast to just saying "I have a UID property".
Depends on changes in libsynthesis and SyncEvolution.
The code also uses a rather ugly pre-processing step of the config:
commit 391e1fd5554fd09597ca3eb626a308db497ec61a
Author: Patrick Ohly <[email protected]>
Date: Tue Nov 16 12:21:08 2010 +0100
local sync: rely on iCalendar 2.0 UID/RECURRENCE-ID for pairing
This patch should be reverted and be replaced by a merge script which compares
the UIDs if (and only if) possible. This is a nicer solution (less code) and
can decide about UID usage after receiving the CtCap (in contrast to the
pre-processing step).
I'd like to get at least the second part into 1.2.
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
