Re: Splitting seahorse into seahorse/seahorse-plugins

["Adam Schreiber" <sadam clemson edu>]

On Jan 12, 2008 5:11 PM, Stef Walter <stef memberwebs com> wrote:
> Now that gnome-keyring has a certificate and key store, it seems
> appropriate that seahorse will start to manage it. I'd like to add code
> to do this during the next GNOME development cycle (ie: 2.24).

Sounds good, with all of these extra secrets floating around there may
be some rearranging of our tab titles and organization.

> Seahorse already has a lot of code, as well as plans and ideas for
> further expansion, and it may be in our interest to separate out the
> various plugins (ie: the actual methods for encryption, decryption,
> signing verification) from the keyring and password management.
>
> It might end up being something like:
>
> seahorse: Key, Certificate and Password Management
>   - seahorse
>   - seahorse-daemon (for the plugins to use)
>   - libcryptui

   - seahorse-preferences

> seahorse-plugins: Crypto operations and integration
>   - gedit plugin
>   - applet
>   - nautilus plugin
>   - epiphany plugin

> I imagine certain parts of libseahorse would be included in
> seahorse-plugins and certain parts would be included in seahorse proper.
> I don't think the actual amount of code overlap is as high as one would
> at first expect.

I would prefer that overlap for things like gconf handling be provided
as a shared item via the magic of svn.  We should try to minimize the
number of places we have to fix bugs.  This might also be a good time
to try and clean up the fd.o standard you had proposed and have
another go at getting it accepted.  If accepted, it could be used for
example in telepathy to provide encryption automatically for any
telepathy clients.

> I imagine seahorse-plugins would depend on seahorse.

Certainly for the preferences bit.

> What do folks think about this idea?

I'm not entirely sure what this gets us, but maybe it could be the
impetus for breaking out a more public facing section of interfaces
from libseahorse that could be used in cases where gpgme is complex
and the DBus interface is too simplistic.  This would also probably
require the full implementation of a proper gpg-agent in gnome-keyring
similarly to what you mentioned in your email to d-d-l.

Cheers,

Adam