On 08/04/14 19:05, Emiliano Heyns wrote:
> On 08/04/2014 18:21:35, "Patrick Ohly" <[email protected]> wrote:
>>> Ah no I understand that, but can a single command set up multiple data
>>> sources?
>> Yes. I think I mentioned the syntax already in this thread, but I don't
>> remember when.
>>
>> --configure backend=eds-events @default calender
>> and
>> --configure backend=eds-contacts @default addressbook
>>
>> can be combined into
>> --configure calendar/eds-event \
>> addressbook/backend=eds-contacts \
>> @default addressbook calendar
> Okay... it's good to know that this can be done, and it answers my
> question, but it maps
>
> --configure backend=b1 @context s1
> --configure backend=b2 @context s2
>
> to
>
> --configure s1/b1 s2/backend=b2 @context s2 s1
>
> for which I can't readily see a rule governing the transformation, so
> I'll take this as noted and stay away from it in my HOWTO.
I think there was a typo in Patrick's example. I think he meant to write:
can be combined into
--configure calendar/backend=eds-event \
addressbook/backend=eds-contacts \
@default addressbook calendar
In other words, when setting source properties on the command line you
can name the property as <source>/<property> in order to set the same
property in different sources to different values.
This sort of thing is more useful where there are also some properties
which are not supposed to be different for different sources (otherwise
the single command doesn't save anything over two separate commands).
So a more common example might be combining
--configure backend=b1 database_user=u @context s1
--configure backend=b2 database_user=u @context s2
into
--configure s1/backend=b1 s2/backend=b2 database_user=u @context s1 s2
Personally I don't use it.
Graham
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
