Hi Patrick,
On Jun 25, 2009, at 17:05 , Patrick Ohly wrote:
I considered this "remote rule" feature rather important for today's
SyncEvolution snapshot, therefore I already went ahead and merged it
into the "master" branches of SyncEvolution and libsynthesis on
moblin.org.
I just pulled from the remote-rules branch you created in indefero. I
assume the patches are the same?
From my point of view that's all ok and I'll merge it.
That libsynthesis branch also contains an update of the configure
build
system: we found that the older libxmltok is source-code compatible
with
expat 2.0, so now it is possible to use that library if installed on
the
system. The bundled source code hasn't changed.
I see - that's sure an improvement.
Would you mind reviewing and integrating these patches into the
upstream
libsynthesis at some point?
Yes, I'm about to do it. I'm just checking your other suggestion about
negative remote rule dependency from earlier in this thread:
On Jun 23, 2009, at 22:55 , Patrick Ohly wrote:
Is there a better way that avoids the dummy property entry?
What about adding support for:
<property name="X-MANAGER" suppressempty="yes"
rule="^EVOLUTION">
<value field="MANAGER" show="yes"/>
</property>
Could be done, only I'd suggest "!" for the NOT char.
The drawback is that multiple not clauses are impossible,
You are referring to the case where you'd have 2 or more remote rules
(say: A,B,C) and would need to express NOT A AND NOT B AND NOT C?
On a second thought, I think the negation is not necessary. Just
insert a catch-all rule at the beginning of the remote rule list with
only <finalrule>no</finalrule> in it. Then you can relate the X-
MANAGER to this rule instead of needing a NOT.
By default, rules are final, i.e. if they match, they become the
selected rule and evaluation stops. If they are set non-final, the
search continues and further rules will be checked, and if one matches
that one becomes selected.
This allows for things like a general rule for all Nokia phones (non-
final), with specialized ones for certain problematic models (final).
Or a default catch-all rule to refer to like in your setup.
Best Regards,
Lukas Zeller ([email protected])
-
Synthesis AG, SyncML Solutions & Sustainable Software Concepts
[email protected], http://www.synthesis.ch
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
