Hi,
We can't rely on distributions packaging, we want our tarballs to be easy to
use.
spice-protocol as is is small, and contains what is required by drivers, agent,
activeX and xpi. So no reason to make it larger. Common will contain what is
required
by the client and server.
Can also be done with some configure magic. When detecting a
non-supported platform or missing build dependencies just skip the build
of server, client or both. Only protcol would be installed unconditionally.
I think separate repos are better though, it makes you think harder when
designing the interfaces between the modules.
That's an ideal goal, but to avoid having to deal with creating a
proper library (with stability garantee etc..), I would start with a
submodule that will slowly move to various clean lib*.
I am out of my depth about this. Hans, Gerd?
Making common/ a proper library probably isn't that easy due to funky
dependencies between common/ and server/+client/. We are probably
better off cleaning up the interfaces before making it a library. Dunno
how much work that is. Starting with a submodule and making it a
library later is an option to handle this ...
cheers,
Gerd
_______________________________________________
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
