[Spice-devel] [PATCH 1/2] Ensure that plugins cannot bypass version check

[Christophe Fergeau]

On Fri, Apr 20, 2018 at 10:10:17AM +0200, Christophe de Dinechin wrote:
> There is no easy way to test if a method is there. There is, however,
> an easy way to test if a C entry point is there in a shared library.
> This is the difference between your scenario and mine. In mine, I can
> explicitly test if the new C entry point is there, and since it has
> been added, I know the plugin is aware of the new semantics. So I can
> then decide to remove the old entry point later, and then I know that
> a version 13 plugin that has the new entry point follows that new
> semantics (in the example I gave, that it knows how to unload).

We introduce the new entry point in version 13, let's say we deprecate
the old semantics at the same time. We can have plugins which switched
to the new semantics, and are built against version 13. We can also have
plugins which still follow the old semantics, and they will still work.
I assume these plugins following the old semantics could be rebuilt
against version 13? And that we can have a plugin with ABI 13 following
the old semantics?
Then in 21, we remove support for the old semantics, and we say that we
still support plugins starting from ABI 13. But what about that plugin
following the old semantics that we rebuilt against ABI 13?

Christophe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/spice-devel/attachments/20180420/5a74272f/attachment.sig>