diff options
author | Karen Arutyunov <karen@codesynthesis.com> | 2019-03-11 16:47:49 +0300 |
---|---|---|
committer | Karen Arutyunov <karen@codesynthesis.com> | 2019-03-11 16:47:49 +0300 |
commit | 3d3a63d289cdaa8bc4d4a3820d499ea5a3205b43 (patch) | |
tree | e608c7ebe88503c670fcec02b6db5f54a6843dd2 /build/bootstrap.build | |
parent | aa5ecc3b21bf88c5b9b9c17912e4efbd96eeab34 (diff) |
Release version 3.18.2+7v3.18.2
Place libsqlite3 and sqlite3 packages into single repository.
Diffstat (limited to 'build/bootstrap.build')
-rw-r--r-- | build/bootstrap.build | 45 |
1 files changed, 0 insertions, 45 deletions
diff --git a/build/bootstrap.build b/build/bootstrap.build deleted file mode 100644 index 255b363..0000000 --- a/build/bootstrap.build +++ /dev/null @@ -1,45 +0,0 @@ -# file : build/bootstrap.build -# copyright : not copyrighted - public domain - -project = libsqlite3 - -# SQLite releases usually have 3-component versions but once in a while they -# will make a 4-component release for what appears to be important bug fixes -# only. So instead of dragging the fourth component around (and confusing a -# lot of people in the process) we will always have three components and will -# handle an occasional bugfix release with a revision. -# -# See also: https://www.sqlite.org/versionnumbers.html -# -# The SQLite documentation says that as long as the major version stays the -# same, then it is backwards-compatible. And since we have the major version -# already embedded into the library name, it doesn't make much sense to repeat -# it. -# -# Note, however, that the binary-compatible API doesn't mean all the builds of -# SQLite are binary-compatible since they can be built with different sets of -# enabled/disabled functionality. In fact, one easy way to break backwards- -# compatibility is to disable some feature that was previously enabled. -# -# So what we seem to need is not an ABI version but an ABI id that identifies -# a specific set of features. And this will not be easy/possible if we want -# to use platform-native versioning (e.g., libsqlite3.so.<num> on Linux). The -# only way to make this work would be to "reserve" some range for build2-based -# builds (e.g., 1000-2000 so that we will have libsqlite3.so.1000; that sure -# looks weird). -# -# Another alternative is to use platform-neutral versioning by embedding the -# id into the library name, similar to '3'. This is probably better since -# there is no "newer" semantics here. While ideally we should use something -# like -build2-0 (i.e., "build2 build, id 0"), that will look rather ugly. So -# we will use just the number but start with -1 in order not to clash with .0 -# used by the autotools build (which becomes -0 on, e.g., Windows; I don't -# believe it will ever be incremented though). -# -abi_major = 1 - -using version -using config -using dist -using test -using install |