summaryrefslogtreecommitdiff
path: root/libtool-version
diff options
context:
space:
mode:
authorAnthony Green <green@moxielogic.com>2009-10-04 23:53:11 -0400
committerAnthony Green <green@moxielogic.com>2009-10-04 23:53:11 -0400
commit5cbe2058c128e848446ae79fe15ee54260a90559 (patch)
treeb9c43875b8197e3b70fb6fa11c9fa8564ff1275c /libtool-version
parentc6dddbd02bad9654ed58cdb0feb360934d105dec (diff)
downloadlibffi-5cbe2058c128e848446ae79fe15ee54260a90559.tar.gz
Initial stand-alone patch.
Diffstat (limited to 'libtool-version')
-rw-r--r--libtool-version25
1 files changed, 24 insertions, 1 deletions
diff --git a/libtool-version b/libtool-version
index 6753286..b8b80e0 100644
--- a/libtool-version
+++ b/libtool-version
@@ -2,5 +2,28 @@
# the libtool manual to understand the meaning of the fields. This is
# a separate file so that version updates don't involve re-running
# automake.
+#
+# Here are a set of rules to help you update your library version
+# information:
+#
+# 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.
+#
+# 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 since the last public
+# release, then set age to 0.
+#
# CURRENT:REVISION:AGE
-4:1:0
+5:10:0