On Wed, 2009-09-16 at 07:33 +0100, Patrick Ohly wrote:
> On Wed, 2009-09-16 at 01:59 +0100, Zhu, Yongsheng wrote:
> > >Yongsheng, do you think we should remove the --keyring command line
> > >parameter in favor of this configuration parameter?
> > For command line, I think we should use keyring=XXX, but we'll have to do
> > some checks.
> > Could it be possible that a platform includes 2 kinds of keyring libraries,
> > gnome-keyring and KDE-keyring?
>
> Yes, this is indeed possible. A full Linux installation can have both
> KDE and GNOME installed completely. The key question is not "what is
> installed" but "what is used by the user who is currently logged in".
The Python keyring library apparently solves this also automatically,
with the possibility to override it:
Configure your keyring lib
The python keyring lib contains implementations for several
backends, including OSX Keychain, Gnome Keyring, KDE Kwallet and
etc. The lib will automatically choose the keyring that is most
suitable for your current environment. You can also specify the
keyring you like to be used in the config file or by calling the
set_keyring() function.
http://pypi.python.org/pypi/keyring/
Probably we can look at the code and use the same mechanism to detect
the "most suitable" keyring - or link in the Python runtime and call the
Python keyring lib (not!).
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
