On Wed, Aug 08, 2018 at 10:10:06AM -0400, Frediano Ziglio wrote: > > > > On 08/08/18 08:12, Christophe Fergeau wrote: > > > On Mon, Jul 30, 2018 at 12:27:35PM -0300, Eduardo Lima (Etrunko) wrote: > > >> +# some global vars > > >> +spice_server_so_version = '1.12.4' > > > > > > How do we update this? With libtool, this was all documented, here it > > > seems it's never going to be updated ;) > > > > In this first moment, I would do it manually, whenever there is a > > release and the version changes, update that value with the new soversion. > > > > In the end it still follows the libtool versioning scheme, not the > > "current:revision:age" per se, but the result of that. I never really > > got involved in updating versions, so if someone can translate that to > > meson, it would be really helpful. > > > > Maybe just a comment pointing to configure.ac for the timing being? The problem is that libtool was doing some magic with the interface age/... from configure.ac, the 1.12.4 meson uses is the result of some computation performed on the numbers which were set in configure.ac. Christophe
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel