From a0cb8991b2cb61e9c0f3d8075759939cc61d57f0 Mon Sep 17 00:00:00 2001
From: Karen Arutyunov <karen@codesynthesis.com>
Date: Tue, 9 Jul 2019 22:02:41 +0300
Subject: Add implementation

---
 libpkgconf/build/bootstrap.build | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 libpkgconf/build/bootstrap.build

(limited to 'libpkgconf/build/bootstrap.build')

diff --git a/libpkgconf/build/bootstrap.build b/libpkgconf/build/bootstrap.build
new file mode 100644
index 0000000..83258e5
--- /dev/null
+++ b/libpkgconf/build/bootstrap.build
@@ -0,0 +1,30 @@
+# file      : build/bootstrap.build
+# copyright : Copyright (c) 2016-2019 Code Synthesis Ltd
+# license   : ISC; see accompanying COPYING file
+
+project = libpkgconf
+
+using version
+using config
+using test
+using install
+using dist
+
+# The versioning scheme (after 0.9.12) assumes that each [major?] release has
+# 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
+#
+# Note that the upstream project didn't increment the release number (3) for
+# the 1.5 library version despite the ABI-breaking changes (issue #15 is
+# reported).
+#
+if ($version.major == 1 && $version.minor == 6)
+  release_num = 4
+else
+  fail "increment the release number?"
-- 
cgit v1.1