I saw the gnom-keyrings is an optional dependency of Seahorse. If 
Seahorse needs to support functionality of g-k-m, does that mean 
Seahorse needs to depend on gnome-keyrings?

Jeff

Adam Schreiber 写道:
> On Dec 13, 2007 2:52 AM, Jeff Cai <[EMAIL PROTECTED]> wrote:
>   
>> Will the gnome-keyrings library be removed from GNOME?
>>     
>
> No, the gnome-keyring module provides the daemon that securely stores
> and hands out the secrets stored in the key rings.
>
>   
>> Can Seahorse
>> manage the keys and secrets that gnome-keyrings operates?
>>     
>
> Yes, Stef just committed the final missing functionality of g-k-m.
>
> Cheers,
>
> Adam
>
>   
>> Jeff
>>
>>
>> On Sat, 2007-12-08 at 23:20 +0000, Stef Walter wrote:
>>     
>>> Seahorse now has surpassed the functionality of gnome-keyring-manager,
>>> as far as managing one or more keyrings and the passwords contained in
>>> them. It does things in a more simple manner, and hopefully more
>>> understandable. Screenshots attached. [1]
>>>
>>> As was discussed before on this list, I'd suggest we remove
>>> gnome-keyring-manager from the 'desktop' distribution for 2.22. The tool
>>> may have uses elsewhere, but I'm not sure we need to duplicate this
>>> functionality in GNOME.
>>>
>>> Cheers,
>>> Stef Walter
>>>
>>> [1] Please feel free to file bugs if you see usability or other issues.
>>>
>>> _______________________________________________
>>> desktop-devel-list mailing list
>>> [email protected]
>>> http://mail.gnome.org/mailman/listinfo/desktop-devel-list
>>>       
>> _______________________________________________
>> desktop-devel-list mailing list
>> [email protected]
>> http://mail.gnome.org/mailman/listinfo/desktop-devel-list
>>
>>     
> _______________________________________________
> desktop-devel-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list
>   

_______________________________________________
desktop-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Reply via email to