On Wed, Sep 26, 2018 at 10:27:00AM +0200, Christophe Fergeau wrote: > On Tue, Sep 25, 2018 at 04:38:26PM -0400, Frediano Ziglio wrote: > > > > > > Fixes the cases where either the dependency is not installed or the > > > version installed does not satisfy the requirement. > > > > > > Signed-off-by: Eduardo Lima (Etrunko) <etrunko@xxxxxxxxxx> > > > > Why this is not true for autoconf? > > > > As spice-protocol is a dependency also for spice-common would be better > > if spice-protocol would be a subproject of spice-common but was > > decided to have spice-protocol as a separate project with its own > > ABI. > > Yes, I'd rather we don't go back to having spice-protocol releases, but > at the same time bundling it with some projects. Ok, not really clear after rereading it. At the moment we have spice-protocol releases and everyone uses that. In my opinion it's better this way, rather than what this patch suggests, where some components would be bundling spice-protocol, and others would still be using the released version. Christophe
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel