On 08/08/18 11:17, Christophe Fergeau wrote: > On Wed, Aug 08, 2018 at 10:42:35AM -0300, Eduardo Lima (Etrunko) 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. > > Well, this is precisely my question ;) I'd like something like > https://gitlab.gnome.org/GNOME/gtk/blob/master/meson.build#L47 This looks good, and since you took the time to search for it, can you provide a patch implementing that for us? ;) > Or maybe we could document something like > https://stackoverflow.com/questions/663209/can-someone-explain-about-linux-library-naming/21462448#21462448 > ? > > Christophe > -- Eduardo de Barros Lima (Etrunko) Software Engineer - RedHat etrunko@xxxxxxxxxx _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel