Guidence from Nicolas Boullis on how to library versioning works or

should work.

lib/Makefile.am

@@ -1,4 +1,4 @@
-#   $Id: Makefile.am,v 1.54 2004/11/06 12:29:37 rocky Exp $
+#   $Id: Makefile.am,v 1.55 2004/11/12 03:44:08 rocky Exp $
 #
 #    Copyright (C) 2003, 2004 Rocky Bernstein <rocky@panix.com>
 #
@@ -20,13 +20,14 @@
 # Things to make the libcdio and libiso9660 libraries
 ########################################################
 #
-# From libtool documentation:
+# From libtool documentation amended with guidance from N. Boullis: 
+#
 #  1. Start with version information of `0:0:0' for each libtool library.
 #
-#  2. 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. 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').
@@ -37,12 +38,13 @@
 #  5. If any interfaces have been added since the last public release,
 #     then increment AGE.
 #
-#  6. If any interfaces have been removed since the last public release,
-#     then set AGE to 0.
+#  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..
 
 libcdio_la_CURRENT := 3
 libcdio_la_REVISION := 0
-libcdio_la_AGE := 2
+libcdio_la_AGE := 0
 
 libiso9660_la_CURRENT := 3
 libiso9660_la_REVISION := 0