[apparmor] [PATCH 7/7] libapparmor: Update library version info

John Johansen john.johansen at canonical.com
Mon Jun 24 21:47:13 UTC 2013

On 06/24/2013 02:34 PM, Seth Arnold wrote:
> On Sun, Jun 23, 2013 at 04:23:19PM -0700, Tyler Hicks wrote:
>> Interfaces were changed, so current is incremented and revision and age
>> are zeroed.
>> Signed-off-by: Tyler Hicks <tyhicks at canonical.com>
> Acked-by: Seth Arnold <seth.arnold at canonical.com>
Hrmm I would even say don't apply this one yet. Or at least if we do we
need to keep it for the rest of the dev cycle and bump again at release.

I realize its hard to follow abi bump rules during dev once you start
rolling packages, so I am okay with doing a bump at the start of the
dev release and then one at the actual release.

The general rules are at the top of the libraries/libapparmor/src/Makefile.am

# variables to set the library versions used by libtool
# Use these rules to update the library version.
# 1. 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.
# 2. If the library source code has changed at all since the last update,
#    then
#    - increment AA_LIB_REVISION
# 3. If any interfaces have been added, removed, or changed since the last
#    update,
#    - increment AA_LIB_CURRENT
#    - set AA_LIB_REVISION to 0.
# 4. If any interfaces have been added since the last public release, then
#    - increment AA_LIB_AGE.
# 5. If any interfaces have been removed or changed since the last public
#    release, then
#    - set AA_LIB_AGE to 0.

More information about the AppArmor mailing list