aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKaren Arutyunov <karen@codesynthesis.com>2017-10-16 12:04:16 +0300
committerKaren Arutyunov <karen@codesynthesis.com>2017-10-16 12:04:16 +0300
commit05e05a89096c0e78b037567f76b2d1fb1877455d (patch)
tree242412efb1067a4a4c16ad82ecbaea13a0248e73
parent1402ef9f02d4271550d23c7b4f205554840721f0 (diff)
Fix package and ABI versions
-rw-r--r--build/bootstrap.build10
-rw-r--r--manifest2
2 files changed, 7 insertions, 5 deletions
diff --git a/build/bootstrap.build b/build/bootstrap.build
index 3034b13..3e632fa 100644
--- a/build/bootstrap.build
+++ b/build/bootstrap.build
@@ -11,15 +11,17 @@ 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.8, version 2 is
+# 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).
+# 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.
#
# See also: http://kaniini.dereferenced.org/2015/07/20/pkgconf-0-9-12-and-future.html
#
-if ($version.major == 1)
- release_num = 2
+if ($version.major == 1 && $version.minor == 4)
+ release_num = 3
else
fail "increment the release number?"
diff --git a/manifest b/manifest
index c241935..da988b1 100644
--- a/manifest
+++ b/manifest
@@ -1,6 +1,6 @@
: 1
name: libpkgconf
-version: 1.3.9-a.0.z
+version: 1.4.0-a.0.z
summary: C library for retriving pkg-config compiler and linker flags
license: ISC, MIT; ISC for the most of original files.
tags: pkg-config, pkgconf, cflags, libs