http://bugzilla.moblin.org/show_bug.cgi?id=3604





--- Comment #2 from pohly <[email protected]>  2009-08-31 03:27:30 ---
(In reply to comment #1)
> fixed in the branch 'origin/bug3604'. waiting for review.

This patch moves the handling of the keyring into the configuration system
inside libsyncevolution. Perhaps I should have been more explicit about this:
the *command line* should access the keyring, not the *core engine*.

The rationale is that there might be multiple, front-end specific ways of
storing passwords (KDE keyring anyone?). We can't support all of them in the
core engine and keep it front-end agnostic at the same time.

Putting GNOME keyring access into the "syncevolution" binary is already
stretching the concept a bit. I can imaging that we'll end up with
--keyring=GNOME and --keyring=KDE at some point, possibly with loadable plugin
modules which do the platform specific keyring access.

That's overkill right now, but i'll be easier to fix if it is not encoded
inside the core engine itself.

What you need to do is implement your own CmdlineSyncClient, derived from
EvolutionSyncClient, and then override the askPassword() method.

Regarding the error if --keyring is requested and not support by the binary:
"ERROR: your system doesn't support keyring. Possibly you may do not use this
parameter or install gnome-keyring on your system."
=>
"ERROR: this syncevolution binary was compiled without support for storing
passwords in a keyring. Either store passwords in your configuration files or
enter them interactively on each program run."

-- 
Configure bugmail: http://bugzilla.moblin.org/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

Reply via email to