Patrick Ohly wrote: > On Wed, 2016-08-24 at 01:22 +0200, deloptes wrote: >> IMO it would be best to push into syncevolution tree and TDE could apply >> own debian rules for building a package which would replace the debian >> native package offering tdepim. >> Does someone has better ideas? > > Sounds like the right approach. I can't promise that I will do anything > with the new backend code (like at least compile-testing it when making > changes) because I'm not sure how much work it would be to make the > dependencies available on my build host, but at least the code would be > available for those who want to use it. >
Last part is nice to have, so that it goes into the distros. I had some discussion with Tino here regarding debian package builds. As I am using debian it would be easy to get a package if the code is in there and just rebuild for trinity desktop. >> The story about ITEM_NEEDS_MERGE however is still a bit unclear to me. Is >> it a suggestion - at least I understand it as such? > > It's a bit more than a suggestion. It's a request to the engine to do > the merge. What happens is: > 1. add new item -> ITEM_NEEDS_MERGE without changing the database > 2. read old item with luid as provided with ITEM_NEEDS_MERGE > 3. update old item with merged data > So in this case I should not DEL+ADD in the backend, but just notify with ITEM_NEEDS_MERGE? Correct? (Sorry I did not have time to look in the other backends how this is exactly implemented). thanks and regards _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
