[Goodies-dev] [Xfce4-commits] <xfce4-sensors-plugin:master> correctly increase library name; version 1.2.3 for entire release

[Yves-Alexis Perez]

On mar., 2011-05-24 at 11:24 +0200, Fabian wrote:
> Updating branch refs/heads/master
>          to bc0738b52f1c2ab434706bf4907e78cf8ef91c9b (commit)
>        from 1717453a5e8df125c2ce86f451f0063224acedd3 (commit)
> 
> commit bc0738b52f1c2ab434706bf4907e78cf8ef91c9b
> Author: Fabian <timystery at arcor.de>
> Date:   Tue May 24 11:23:37 2011 +0200
> 
>     correctly increase library name; version 1.2.3 for entire release
> 
>  configure.in.in |   11 ++++++-----
>  1 files changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/configure.in.in b/configure.in.in
> index ceeddfd..fff87e9 100644
> --- a/configure.in.in
> +++ b/configure.in.in
> @@ -7,14 +7,14 @@ dnl 2003,2004, 2007 Benedikt Meurer <benny at xfce.org>
>  dnl 2007-2011 Fabian Nowak <timystery at arcor.de>
>  dnl
>  
> -m4_define([libxfce4sensors_verinfo], [1:2:1])
> +m4_define([libxfce4sensors_verinfo], [3:2:2]) 

Not sure if this is what you really intended, again, since this leads
to /usr/lib/xfce4/modules/libxfce4sensors.so.1.2.2.

If you upgrade the first number ('current') then you must reset the
second ('revision') to 0.

You can see http://sourceware.org/autobook/autobook/autobook_91.html for
more info on this. The following rules usually apply:

----
Here are a set of rules to help you update your library version information:

Start with version information of `0:0:0' for each libtool library.
Update the version information only immediately before a public release of your software. More frequent updates are unnecessary, and only guarantee that the current interface number gets larger faster.
If the library source code has changed at all since the last update, then increment revision (`c:r:a' becomes `c:r+1:a').
If any interfaces have been added, removed, or changed since the last update, increment current, and set revision to 0.
If any interfaces have been added since the last public release, then increment age.
If any interfaces have been removed since the last public release, then set age to 0.

Never try to set the interface numbers so that they correspond to the
release number of your package. This is an abuse that only fosters
misunderstanding of the purpose of library versions. Instead, use the
`-release' flag (see section 6.4 Managing release information), but be
warned that every release of your package will not be binary
compatibility with any other release.
---

Regards,
-- 
Yves-Alexis