From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/adodb/
Date: Tue, 30 Jul 2019 22:32:00 +0000 (UTC) [thread overview]
Message-ID: <1564525911.8cf09e93f7c2dac9439589df92289a3862367c0a.whissi@gentoo> (raw)
commit: 8cf09e93f7c2dac9439589df92289a3862367c0a
Author: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 30 22:16:52 2019 +0000
Commit: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Tue Jul 30 22:31:51 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8cf09e93
dev-php/adodb: bump to v5.20.14
Package-Manager: Portage-2.3.69, Repoman-2.3.16
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>
dev-php/adodb/Manifest | 1 +
dev-php/adodb/adodb-5.20.14.ebuild | 40 ++++++++++++++++++++++++++++++++++++++
2 files changed, 41 insertions(+)
diff --git a/dev-php/adodb/Manifest b/dev-php/adodb/Manifest
index 022744eec1a..c92d3593bb8 100644
--- a/dev-php/adodb/Manifest
+++ b/dev-php/adodb/Manifest
@@ -1,3 +1,4 @@
DIST adodb-5.20.12.tar.gz 464962 BLAKE2B 51b1bec4c9bda427988848cd0ff810058e159c75946ea4d14d1ab639545f0c95a8a1a2b8193c8c0403e37fc2e3b858f97b255b9b615b65786d1593269e9da731 SHA512 ac8f36dba459bac15f16ecfd1ece69edc922e67b6aec3641a0c8ffc50c6b1c437ecce2e5652c31f2e472f7abefb3ac5a8a2bef188959007442799784ab764c1e
DIST adodb-5.20.13.tar.gz 465568 BLAKE2B 7acfe36586fcf0e0291ce9dd6446c6f0922b9c7144b86d8eb0d78db98247fc9ac6aa9b1623822628096c2be0e0e9c554e9c3acbc05d9ddcda1b5c598b8b3652b SHA512 0824de6abf73a8e3fbdde30ca1455264a49e3b711e81c8232bd82c082c0d3f255aea35a167685cd01e80216622db1167c17a518d57b1ed260eaa498cab0b9fca
+DIST adodb-5.20.14.tar.gz 465896 BLAKE2B acd8494141584b0c02c2e30aa59b3916ae811b8095ca724d22f44ed2cb1456b8e8afc7ff9af41e7476f4a93809e762c44a175fd3775b69654107813342b3a47a SHA512 fa9b764742f3edf15e79da7a34ca52b19f51454fa20bc963cce963cdd40f7e78671e993cd672a21e9917aa2440c63601fbf768b5259dccb64b458a5be6f4b0eb
DIST adodb-5.20.9.tar.gz 464257 BLAKE2B 38a37e4a5b1ac86b37cbd164c79e2112c78fb22530a225d2cac4f916703d4c2bd300a47a214344d8ae9e5c94467ec34cab96ab36a10ad8dad581ec74c73ae111 SHA512 bc40113012c27b759ff35e7395404d1756720e9daef7df4d33147b9950e9ffd032274ccd8808fe303ba75feeaf727e2deb50fc6d79826db96ce568a70007f30f
diff --git a/dev-php/adodb/adodb-5.20.14.ebuild b/dev-php/adodb/adodb-5.20.14.ebuild
new file mode 100644
index 00000000000..f16a3af534d
--- /dev/null
+++ b/dev-php/adodb/adodb-5.20.14.ebuild
@@ -0,0 +1,40 @@
+# Copyright 1999-2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+MY_PN="ADOdb"
+DESCRIPTION="Database abstraction layer for PHP"
+HOMEPAGE="https://github.com/ADOdb"
+SRC_URI="https://github.com/${MY_PN}/${MY_PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="BSD LGPL-2.1+"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
+IUSE=""
+
+# If you want to be picky, we should require that PHP be built with at
+# least one database driver enabled; otherwise adodb isn't going to be
+# able to do anything. But, the database USE flags for dev-lang/php are
+# a mess. What we would *like* to do is have a set of USE flags for
+# adodb that then propagate to PHP itself... for example, adodb[mysql]
+# could require php[mysql]. To do that would require that we duplicate
+# the database USE flag mess for adodb -- not desirable. Instead we punt
+# and let the user install adodb unconditionally. If he doesn't have
+# database support in PHP, it just won't work.
+RDEPEND="dev-lang/php:*"
+
+S="${WORKDIR}/${MY_PN}-${PV}"
+
+src_install() {
+ DOCS="README.md docs/changelog*.md xmlschema*.dtd session/*.sql"
+ DOCS+=" session/*.txt session/*.xml pear/auth_adodb_example.php"
+ DOCS+=" pear/readme.Auth.txt"
+
+ dodoc $DOCS
+ rm -f $DOCS || die "failed to remove docs before installation"
+
+ insinto "/usr/share/php/${PN}"
+ doins *.php
+ doins -r contrib datadict drivers lang pear perf replicate session xsl
+}
next reply other threads:[~2019-07-30 22:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 22:32 Thomas Deutschmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-03 19:48 [gentoo-commits] repo/gentoo:master commit in: dev-php/adodb/ Michael Orlitzky
2024-08-03 19:48 Michael Orlitzky
2024-06-11 11:36 Arthur Zamarin
2024-03-24 14:00 Michael Orlitzky
2024-03-24 14:00 Michael Orlitzky
2023-08-29 7:49 Conrad Kostecki
2023-06-10 1:26 Michael Orlitzky
2023-06-09 17:54 Arthur Zamarin
2022-08-07 13:13 Michael Orlitzky
2022-08-07 13:13 Michael Orlitzky
2022-08-07 13:13 Michael Orlitzky
2022-08-07 13:13 Michael Orlitzky
2022-01-30 15:22 Michael Orlitzky
2021-04-25 15:36 Thomas Deutschmann
2021-02-01 22:00 Thomas Deutschmann
2020-08-06 14:34 Thomas Deutschmann
2020-08-06 14:34 Thomas Deutschmann
2020-06-14 23:30 Thomas Deutschmann
2020-01-21 23:51 Michael Orlitzky
2019-12-26 10:23 Thomas Deutschmann
2019-07-30 22:32 Thomas Deutschmann
2019-07-30 22:32 Thomas Deutschmann
2018-09-04 0:25 Brian Evans
2018-04-24 18:19 Brian Evans
2017-05-27 23:01 Brian Evans
2017-01-21 17:02 Michael Orlitzky
2017-01-21 11:42 Jeroen Roovers
2017-01-21 11:42 Jeroen Roovers
2017-01-07 1:54 Aaron Bauman
2017-01-05 12:37 Tobias Klausmann
2017-01-05 1:15 Michael Orlitzky
2016-07-16 14:15 Michael Orlitzky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1564525911.8cf09e93f7c2dac9439589df92289a3862367c0a.whissi@gentoo \
--to=whissi@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox