aboutsummaryrefslogtreecommitdiff
path: root/build
diff options
context:
space:
mode:
authorKaren Arutyunov <karen@codesynthesis.com>2018-06-06 15:41:51 +0300
committerKaren Arutyunov <karen@codesynthesis.com>2018-06-06 15:41:51 +0300
commit9fcd9687814f12770487d03dd0a61d42fc6ad693 (patch)
treefa44411615f6bdc87eea6872de8f3cdd469d63e4 /build
parent034f19cda78286fc676bb4a6116a66f7d5edd453 (diff)
Merge with 1.4.2 upstream package version
Diffstat (limited to 'build')
-rw-r--r--build/bootstrap.build13
1 files changed, 6 insertions, 7 deletions
diff --git a/build/bootstrap.build b/build/bootstrap.build
index 57fd2bd..e51f606 100644
--- a/build/bootstrap.build
+++ b/build/bootstrap.build
@@ -11,13 +11,12 @@ using test
using install
# The versioning scheme (after 0.9.12) assumes that each [major?] release has
-# it's own number (starting with 2). In any case, as of 1.3.9, version 2 is
-# still in the library file name (libpkgconf.so.2.0.0). This probably means
-# that the release number is equal to major version + 1 (though in Makefile.am
-# they use -version-info 2:0:0 which doesn't mean what they think it means). Or
-# it can mean that the first two release version components constitute a major
-# version, and the release number increments each time this version changes.
-# So we just need to watch their Makefile.am for any changes.
+# it's own number (starting with 2). In any case, for the 1.3.90 to 1.4.0
+# release version increment the version in the library file name changed from
+# 2 to 3 (libpkgconf.so.2.0.0 -> libpkgconf.so.3.0.0). This probably means
+# that the first two release version components constitute a major version,
+# and the release number increments each time this version changes. So we just
+# need to watch their Makefile.am for any changes.
#
# See also: http://kaniini.dereferenced.org/2015/07/20/pkgconf-0-9-12-and-future.html
#