Yeah, this idea is good to me and I think it's very useful because we support many
backends, which give
us the power to access different kinds of data storage.
Some questions or concerns here:
--print-items shows all existing items using one line per item using
the format "<luid>: <short description>".
It is good enough
to show all items. But what if we want to see a full description of one item?
Is it possible to add an option like this "--print-item <config> <source>
syncevolution [--delimiter <string>] --export
<dir>|<file>|- <config> <source>
syncevolution [--delimiter <string>|none] --import <dir>|<file>|-
We only support import from or export to a file/directory though
file backend, do we?
If no, how to specific what backend to be used for the items in the file?
Another thing is that what if we want to delete an item?
A possible solution is to use a '--update' option with an empty item to replace
the existing one.
But I think a warning is needed to notify users.