[Libcdio-devel] Getting libcdio/vcdimager library revision numbers correct

[R. Bernstein]

In preparing for a release, I've been trying to determine what library
version numbers to use in libcdio and vcdimager.

Here's the general information I have with guidance from N. Boullis: 

#  1. Start with version information of `0:0:0' for each libtool library.
#
#  2. It is probably not a good idea to update the version information 
#     several times between public releases, but rather once per public
#     release. (This seems to be more an aesthetic consideration than
#     a hard technical one.)
#
#  3. If the library source code has changed at all since the last
#     update, then increment REVISION (`C:R:A' becomes `C:R+1:A').
#
#  4. If any interfaces have been added, removed, or changed since the
#     last update, increment CURRENT, and set REVISION to 0.
#
#  5. If any interfaces have been added since the last public release,
#     then increment AGE.
#
#  6. If any interfaces have been removed or changed since the last
#     public release, then set AGE to 0. A changed interface means an
#     incompatibility with previous versions.

For libcdio and this release, a couple of variables (which effect the
timeouts on MMC commands) was added. And of course library code was
added for this and other small bug fixes.

Right now we have:

libcdio_la_CURRENT := 5
libcdio_la_REVISION := 0
libcdio_la_AGE := 0

or 5:0:1

Rule 3 applies so we'd have 5:0:1; I'm not sure if adding the
variables constitutes an "interface adition" or "interface change". If
so, we'd get by Rules 4, and 5: 6:0:1. I'm not sure if Rule 6
applies. I'm assuming that an addition of a variable is not a "change"
in the sense of Rule 6. (But if rule 6 applies we'd get 6:0:0).

For vcdimager libvcdinfo code was changed and a new interface was
added. So I guess we go from 1:1:1 to 2:0:0.

Comments?