Re: Reorganizing seahorse source code

["Adam Schreiber" <sadam clemson edu>]

On Wed, Apr 16, 2008 at 8:47 PM, Stef Walter <stef-list memberwebs com> wrote:
>  I was thinking about something along these lines:
>
>  /tags
>  /branches
>  /trunk
>  /plugins
>    /branches
>    /tags
>    /trunk
>
>  What does everyone think about this plan?

That sounds fine to me.  How will libseahorse be split up?  A lot of
the plugins have been migrated to libcryptui and the DBus interface,
but some things still make direct calls.

On a different note:

I started the process of cooking up some python bindings for
libcryptui.  They don't compile yet, but they'll need a home at some
point.  They depend on libcryptui being present, but don't need to be
built in the same tree.  I've been calling them pycryptui.  If someone
wants to look at them I can provide a tarball or get them into a gnome
svn module.  *Warning* I'm learning how to create bindings and some
things about python at the same time so someone with python experience
should probably go over them before a release is made.

Cheers,

Adam