And how does any of that not make it not a submodule? - Used by multiple modules: yes, that’s precisely what submodules are for (that’s also the case for spice-common). - Has a stable API: yes, but when we need to change it, it would be nice to have that the change recorded in git history of the modules using it. For example, a lot of the streaming work requires a branched-off spice-protocol. I was also wondering about protocol updates being easier to do in a consistent way if spice-protocol was “above” spice-serverr and spice-gtk. Which could be solved by having a submodule structure like: spice spice-protocol spice-common spice-server spice-gtk instead of the current: (nothing) spice-protocol spice (not called spice-server) spice-common spice-gtk spice-common Christophe
|
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel