From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/adodb/
Date: Sun, 30 Jan 2022 15:22:27 +0000 (UTC) [thread overview]
Message-ID: <1643556063.d52de2552e38f4bd8dcf9c4721731e355b6b0f01.mjo@gentoo> (raw)
commit: d52de2552e38f4bd8dcf9c4721731e355b6b0f01
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 30 15:20:26 2022 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sun Jan 30 15:21:03 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d52de255
dev-php/adodb: new upstream release to fix CVE-2021-3850.
Bug: https://bugs.gentoo.org/832208
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
dev-php/adodb/Manifest | 1 +
dev-php/adodb/adodb-5.21.4.ebuild | 40 +++++++++++++++++++++++++++++++++++++++
2 files changed, 41 insertions(+)
diff --git a/dev-php/adodb/Manifest b/dev-php/adodb/Manifest
index c55bc9321fb1..39d2df6f3e60 100644
--- a/dev-php/adodb/Manifest
+++ b/dev-php/adodb/Manifest
@@ -2,3 +2,4 @@ DIST adodb-5.20.14.tar.gz 465896 BLAKE2B acd8494141584b0c02c2e30aa59b3916ae811b8
DIST adodb-5.20.18.tar.gz 467003 BLAKE2B ea0b007359a4fdada0fface3d5af82c335f2e7efeacdbb66be37914d76bff2783b58b2318531c527d13c3c358800803385c660c8f9372cf4a49269ed7e0c7d51 SHA512 09b04987e20a674a202be3889523b3bada578ea01f07830fed15afafb046687004b4e305a6abf2af795a7b0e3563f6e8afec5b0189f21e5c74b5e84bfbee1cd9
DIST adodb-5.20.20.tar.gz 469337 BLAKE2B cffe367e498978b095e28bab565c8af7e02769e4c76977fae7d807c6326d9b4679e319fa84debc9b250d0548e7dcac2e078b4968160490831e2390ce86fbe229 SHA512 2578a594bf9f1b33b5a78bd3e52b9fb73d0457b021a2bca6b5f8d311c0ecb347968a928a1dabd2c8806972dda6ec535fec94d6f792b6f5398aeff587321e5113
DIST adodb-5.21.0.tar.gz 437724 BLAKE2B addd14c45ec3e1a3fcda63065ccbf06a6627fcf498a3aecc609c7763627915904c241bcb2db1c3aa31ba228b35d788885fd09311e2353f7490e31cee070f607e SHA512 305b5395e4d47d86bbb689818fee44a2b970d081e9ab527f7d0b010b5ae1159eac32c125d5b303569afa2a4360e160c37e17ff7c5adb7566175f9f131393643c
+DIST adodb-5.21.4.tar.gz 435699 BLAKE2B 7025a7ba322840d62e5b2b3f9e5933d89560a0eff52f0d77976ca442080e7a6a6d778d4fa106357ab68b4f207c98503854f601f579c0c11ee27fb52da5f53519 SHA512 0142ffa0dad1275780aadbc1ad702870b977eb141321f19c265310284d6d4a0820653e77fb3b4ce002dcc42fa952546e90428dff4f931a2bb2a83031bd818f01
diff --git a/dev-php/adodb/adodb-5.21.4.ebuild b/dev-php/adodb/adodb-5.21.4.ebuild
new file mode 100644
index 000000000000..a3135caca47d
--- /dev/null
+++ b/dev-php/adodb/adodb-5.21.4.ebuild
@@ -0,0 +1,40 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+MY_PN="ADOdb"
+DESCRIPTION="Database abstraction layer for PHP"
+HOMEPAGE="https://adodb.org/ https://github.com/ADOdb/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 datadict drivers lang pear perf session xsl
+}
next reply other threads:[~2022-01-30 15:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 15:22 Michael Orlitzky [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
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
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=1643556063.d52de2552e38f4bd8dcf9c4721731e355b6b0f01.mjo@gentoo \
--to=mjo@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