Hi Patrick,
On Jun 25, 2009, at 18:39 , Patrick Ohly wrote:
Better pull "master" from moblin.org. I didn't mean to push into
indefero and the copy there might be older.
Hmm, I'm trying to use the new expat header check and it fails on
Moblin. HAVE_EXPAT is not set although it should. Better hold of
merging
this.
Just let me know when you think it's ok.
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?
Yes.
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.
Sorry, I don't follow here. Can you give an example?
If I understood the problem correctly, what you want is X-MANAGER only
to show up in the sync case, but not the "EVOLUTION" case.
So you need a rule that is active during sync data generation. This is
why I suggested a rule that is always active in sync, e.g. named
"sync". You can then make the X-MANAGER property depend on "sync":
<property name="X-MANAGER" suppressempty="yes" rule="sync">
<value field="MANAGER" show="yes"/>
</property>
This way, it will be active in "sync", and inactive in "EVOLUTION" case.
However, I don't think it would help: the remote rule is activate in
the
macros via its name. The content of the rule (finalrule,
suppressempty,
ID, ...) is completely ignored.
Yes, for the EVOLUTION case. But for the sync case, the normal
selection procedure (based on devInf) will be run.
I wanted to use suppressempty as default when generating items for
Evolution, but because the profile handler only copies those
settings if
a related datastore is given.
You could add it as a bitmap option to the mode parameter, so you can
set it when calling MAKETEXTWITHPROFILE().
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
