https://bugs.meego.com/show_bug.cgi?id=14805
Summary: relax need for template during configuration
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: critical
Priority: Undecided
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
Currently SyncEvolution insists on having a template when creating a config
from scratch. This was meant to address typos like "--configure sheduleworld".
But when the command line contains enough information, no template is needed.
The same logic was applied to configuring a source: if a source is not among
those defined by the template, configuring it is rejected as a typo.
I suggest to add "--template none" as a special case. If that argument is
given, then SyncEvolution shall suppress the errors and create a config based
on the command line properties (whatever those are).
If a source is among those which has command line properties, it shall also be
accepted.
If the sync properties contain the obligatory properties, the "need template"
error shall also be skipped. Obligatory at this time: only "syncURL".
Examples:
--configure foobar => error "need template"
--configure --template none foobar => empty "foobar" peer config, no sources
configured
--configure ical20/backend=calendar foobar => "foobar" peer config with source
"ical20"
--configure syncURL=local://@foo bar => "foo" peer config, no sources
configured
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
