Ok, so take three:

(1) spice-protocol - remains unchanged. specifically, despite the
name, will not contain the .proto nor the python codegen bits nor the
generated files.

(2) spice-common (repository spice/common) - new repository,
contains: spice*.proto spice_codegen.py and friends (python_modules
subdir) produces a proper shared library, used by spice-server,
spice-client, spice-gtk, named libspice-common.so.0, containing
marshalling and rendering code (including any decoder/encoder) plus
anything else currently in common (like ssl-verify).

(3) spice-client - breakoff client subdir from current spice (maybe
rename+remove-the-rest to keep history)

(4) spice-server - rename current spice repo (just to keep history)

(5) spice-gtk - remains, just move it to freedesktop now that we want
to keep it.

(6) spice-all - convenience repository that has the rest as
submodules and has a helpful makefile to build them all.

The rest of the repos will need to be updated. Concrete steps would
be:

(1) create spice/spice-common, spice/spice-server,
spice/spice-client, spice/spice-gtk repositories (btw - any comments
on the spice- prefix?)

(2) get spice-common to build, the rest to use

(3) remove the "spice/spice" repository

(4) make spice-all

Comments?

Looks good to me.

cheers,
  Gerd

_______________________________________________
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel

Reply via email to