Date: Friday, January 31, 2020 @ 12:29:14
  Author: foxboron
Revision: 560749

archrelease: copy trunk to community-x86_64

Added:
  sqlite-replication/repos/community-x86_64/
  sqlite-replication/repos/community-x86_64/PKGBUILD
    (from rev 560748, sqlite-replication/trunk/PKGBUILD)
  sqlite-replication/repos/community-x86_64/license.txt
    (from rev 560748, sqlite-replication/trunk/license.txt)

-------------+
 PKGBUILD    |   53 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 license.txt |   33 +++++++++++++++++++++++++++++++++
 2 files changed, 86 insertions(+)

Copied: sqlite-replication/repos/community-x86_64/PKGBUILD (from rev 560748, 
sqlite-replication/trunk/PKGBUILD)
===================================================================
--- community-x86_64/PKGBUILD                           (rev 0)
+++ community-x86_64/PKGBUILD   2020-01-31 12:29:14 UTC (rev 560749)
@@ -0,0 +1,53 @@
+# Maintainer: Thomas Hipp <thomashipp at gmail dot com>
+# Maintainer: Andreas Radke <andy...@archlinux.org>
+# Contributor: Tom Newsom <jeeps...@gmx.co.uk>
+
+pkgname="sqlite-replication"
+pkgver=3.30.1
+pkgrel=2
+_replication=4
+pkgdesc="Replication Enabled SQL Database Engine in a C Library"
+arch=('x86_64')
+license=('custom:Public Domain')
+url="https://github.com/canonical/sqlite";
+depends=('readline' 'zlib')
+makedepends=('tcl')
+source=("https://github.com/canonical/sqlite/archive/version-${pkgver}+replication${_replication}.tar.gz";
+        license.txt)
+sha256sums=('e9ab0542396be10e1b2951423f13b3e4d118a18e5d4ef39dc271e7dd17d3910f'
+            '4e57d9ac979f1c9872e69799c2597eeef4c6ce7224f3ede0bf9dc8d217b1e65d')
+
+build() {
+  export CPPFLAGS="$CPPFLAGS -DSQLITE_ENABLE_COLUMN_METADATA=1 \
+                             -DSQLITE_ENABLE_UNLOCK_NOTIFY \
+                             -DSQLITE_ENABLE_DBSTAT_VTAB=1 \
+                             -DSQLITE_ENABLE_FTS3_TOKENIZER=1 \
+                             -DSQLITE_SECURE_DELETE \
+                             -DSQLITE_MAX_VARIABLE_NUMBER=250000 \
+                             -DSQLITE_MAX_EXPR_DEPTH=10000"
+
+  # build sqlite
+  cd sqlite-version-${pkgver}-replication${_replication}
+  ./configure --prefix=/usr \
+       --libdir=/usr/lib/$pkgname \
+       --includedir=/usr/include/$pkgname \
+       --disable-static \
+       --disable-amalgamation \
+       --enable-fts3 \
+       --enable-fts4 \
+       --enable-fts5 \
+       --enable-rtree \
+       --enable-json1 \
+       --enable-replication
+  make
+}
+
+package() {
+  cd sqlite-version-${pkgver}-replication${_replication}
+  make DESTDIR="${pkgdir}" install
+
+  install -D -m644 "${srcdir}/license.txt" 
"${pkgdir}/usr/share/licenses/${pkgbase}/license.txt"
+
+  rm -rf "${pkgdir}/usr/bin"
+  rm -rf "${pkgdir}/usr/lib/tcl"*
+}

Copied: sqlite-replication/repos/community-x86_64/license.txt (from rev 560748, 
sqlite-replication/trunk/license.txt)
===================================================================
--- community-x86_64/license.txt                                (rev 0)
+++ community-x86_64/license.txt        2020-01-31 12:29:14 UTC (rev 560749)
@@ -0,0 +1,33 @@
+SQLite Copyright
+SQLite is in the
+Public Domain 
+
+
+All of the deliverable code in SQLite has been dedicated to the public domain 
by the authors. All code authors, and representatives of the companies they 
work for, have signed affidavits dedicating their contributions to the public 
domain and originals of those signed affidavits are stored in a firesafe at the 
main offices of Hwaci. Anyone is free to copy, modify, publish, use, compile, 
sell, or distribute the original SQLite code, either in source code form or as 
a compiled binary, for any purpose, commercial or non-commercial, and by any 
means. 
+
+The previous paragraph applies to the deliverable code in SQLite - those parts 
of the SQLite library that you actually bundle and ship with a larger 
application. Portions of the documentation and some code used as part of the 
build process might fall under other licenses. The details here are unclear. We 
do not worry about the licensing of the documentation and build code so much 
because none of these things are part of the core deliverable SQLite library. 
+
+All of the deliverable code in SQLite has been written from scratch. No code 
has been taken from other projects or from the open internet. Every line of 
code can be traced back to its original author, and all of those authors have 
public domain dedications on file. So the SQLite code base is clean and is 
uncontaminated with licensed code from other projects. 
+Obtaining An Explicit License To Use SQLite
+
+Even though SQLite is in the public domain and does not require a license, 
some users want to obtain a license anyway. Some reasons for obtaining a 
license include: 
+You are using SQLite in a jurisdiction that does not recognize the public 
domain. 
+You are using SQLite in a jurisdiction that does not recognize the right of an 
author to dedicate their work to the public domain. 
+You want to hold a tangible legal document as evidence that you have the legal 
right to use and distribute SQLite. 
+Your legal department tells you that you have to purchase a license. 
+
+If you feel like you really have to purchase a license for SQLite, Hwaci, the 
company that employs the architect and principal developers of SQLite, will 
sell you one. 
+Contributed Code
+
+In order to keep SQLite completely free and unencumbered by copyright, all new 
contributors to the SQLite code base are asked to dedicate their contributions 
to the public domain. If you want to send a patch or enhancement for possible 
inclusion in the SQLite source tree, please accompany the patch with the 
following statement: 
+The author or authors of this code dedicate any and all copyright interest in 
this code to the public domain. We make this dedication for the benefit of the 
public at large and to the detriment of our heirs and successors. We intend 
this dedication to be an overt act of relinquishment in perpetuity of all 
present and future rights to this code under copyright law. 
+
+We are not able to accept patches or changes to SQLite that are not 
accompanied by a statement such as the above. In addition, if you make changes 
or enhancements as an employee, then a simple statement such as the above is 
insufficient. You must also send by surface mail a copyright release signed by 
a company officer. A signed original of the copyright release should be mailed 
to:
+Hwaci
+6200 Maple Cove Lane
+Charlotte, NC 28269
+USA 
+
+A template copyright release is available in PDF or HTML. You can use this 
release to make future changes.
+
+see http://www.sqlite.org/copyright.html
\ No newline at end of file

Reply via email to