[PATCH] Add version info to the shared libs

[Jan Engelhardt]

On Tuesday 2012-11-20 20:59, Mikko Levonmaa wrote:
>
>What I was actually trying to propose in my previous mail is that
>even when the current api version is 0 we could already have the
>mechanics in place to increment the api version when the time comes,
>or is that automatically handled?

It is not automatically handled. One could probably craft some
code, but it's usually not worth the time. Manual updating is
sufficient for most people.

>If it is not, then we need to set
>the version info (current, revision and age) eventually. So the
>patch would be like
>
>.... -version-info @WAYLAND_API_CUR@:@WAYLAND_API_REV@:@WAYLAND_API_AGE@

I don't quite see the use of the @API_CUR@ indirection.
Just put -version-info 1:0:0 when the time comes.

>The rational on my side for the original, albeit flawed suggestion,
>was that libtools docs suggest to update the version information
>only immediately before a public release.

That rule does not apply to the very first public release as there is no 
prior release.