[gentoo-commits] repo/gentoo:master commit in: dev-php/smarty/

public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed

From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/smarty/
Date: Thu,  2 May 2019 22:40:12 +0000 (UTC)	[thread overview]
Message-ID: <1556836780.d38cf949be695e971aa9d35dcdeb806eb509469b.mjo@gentoo> (raw)

commit:     d38cf949be695e971aa9d35dcdeb806eb509469b
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Thu May  2 22:39:40 2019 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Thu May  2 22:39:40 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d38cf949

dev-php/smarty: remove old vulnerable versions.

Bug: https://bugs.gentoo.org/666440
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11

 dev-php/smarty/Manifest             |  3 ---
 dev-php/smarty/smarty-3.1.30.ebuild | 46 -------------------------------------
 dev-php/smarty/smarty-3.1.31.ebuild | 46 -------------------------------------
 dev-php/smarty/smarty-3.1.32.ebuild | 46 -------------------------------------
 4 files changed, 141 deletions(-)

diff --git a/dev-php/smarty/Manifest b/dev-php/smarty/Manifest
index 1006772fc49..8a87b2c4360 100644
--- a/dev-php/smarty/Manifest
+++ b/dev-php/smarty/Manifest
@@ -1,5 +1,2 @@
 DIST manual-en.3.1.14.zip 408414 BLAKE2B 03d4e7a386eb3bd5b19e5c555ec34b86812838a5b5fac8ec0ab9701fba89a5867714da57d950f68224a89bbe2267c18d638ee850681860de309c74bbfb3d0a0b SHA512 d384e3856b45ed3f992f3732a5465120abe9fb947cdf13ff67a9c4264f72987d24885ee61cd7309b728e64cdfe4f34c3e7f757096d35de56d962f3b78def9e58
-DIST smarty-3.1.30.tar.gz 255464 BLAKE2B 8378e6336f271e3c41e16b8fbb70356827ff4a9a61e3cf2a23fdbd0617155ec9dca6a5b6372327d4b35a5c6f7c3b58e807afe7403b7ed929ebacfb3c36e124d0 SHA512 6ad9a6cf10b81fecbdc4daa4acbd9724db5f1c2a014e35039b36b0bf00ba000946a2126f7da5899e587a79419f451aafcd1ee14597a32cf290bbd0bf13a877d0
-DIST smarty-3.1.31.tar.gz 244196 BLAKE2B 695bd40d337e8f2d4a44a7b30b743ab4e5b6a7b024a514de956cd513dd6639ac6f9ae464f0d3b4cfcaf7de17994837a866cdd4945780bd3a96ff32df300302a3 SHA512 807343e4229413ea0f5219a828d4e91603fb5454f4abe8aa2d41f0a6fe32fa476e791340e1e95178ded3774d1524e98489c104c6fa391e70a8225de28fdcca18
-DIST smarty-3.1.32.tar.gz 250680 BLAKE2B 92d4942f2d3d802b18082f5f6079c8b6945abadd8ef2c87ea217b106eeeedfbde7f1bd00c6fced67b73fc3cf328ec91fc1fb61c7f991b992167fa9d2fb1f2ad2 SHA512 07c95177172718158b9b562c6d8ff79566f4bd8e07ba394cc82c52dec7ec869935fd03ce523115c08472159adf68b902d1db5f8543201a35adf22027c5978080
 DIST smarty-3.1.33.tar.gz 249999 BLAKE2B 1e174b190238c8b20d5dae9c0c9fdf264c4716ba850599a2a028fe6c307eb3d9d2611e3b928efb9471e051496e4e31502458cd7a71a9318e012d5af7eca2c50e SHA512 443473cf12c7e053744daef7a70d4172979d760278aa1593216d0b70f0c12ca2b48eb79486a1c10a1cf2264da671804b94ee9d538b9013ff0bdc42e28639ca5d

diff --git a/dev-php/smarty/smarty-3.1.30.ebuild b/dev-php/smarty/smarty-3.1.30.ebuild
deleted file mode 100644
index 8d68f8465a4..00000000000
--- a/dev-php/smarty/smarty-3.1.30.ebuild
+++ /dev/null
@@ -1,46 +0,0 @@
-# Copyright 1999-2018 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-DOC_PV="3.1.14"
-
-DESCRIPTION="A template engine for PHP"
-HOMEPAGE="https://www.smarty.net/"
-SRC_URI="https://github.com/smarty-php/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz
-	doc? ( https://www.smarty.net/files/docs/manual-en.${DOC_PV}.zip )"
-
-LICENSE="LGPL-3"
-SLOT="0"
-KEYWORDS="alpha amd64 hppa ia64 ppc ppc64 sparc x86"
-IUSE="doc"
-
-DEPEND="doc? ( app-arch/unzip )"
-
-# PHP unicode support is detected at runtime, and the cached templates
-# that smarty generates depend on it. If, later on, PHP is reinstalled
-# without unicode support, all of the previously-generated cached
-# templates will begin to throw 500 errrors for missing mb_foo
-# functions. See bug #532618.
-RDEPEND="dev-lang/php:*[unicode]"
-
-src_install() {
-	insinto "/usr/share/php/${PN}"
-	doins -r libs/*
-
-	local DOCS=( *.txt README README.md )
-	local HTML_DOCS
-	use doc && HTML_DOCS="${WORKDIR}/manual-en/"*
-	einstalldocs
-}
-
-pkg_postinst() {
-	elog "${PN} has been installed in /usr/share/php/${PN}/."
-	elog
-	elog 'To use it in your scripts, include the Smarty.class.php file'
-	elog "from the \"${PN}\" directory; for example,"
-	elog
-	elog "  require('${PN}/Smarty.class.php');"
-	elog
-	elog 'After that, the Smarty class will be available to you.'
-}

diff --git a/dev-php/smarty/smarty-3.1.31.ebuild b/dev-php/smarty/smarty-3.1.31.ebuild
deleted file mode 100644
index c1b265f15ea..00000000000
--- a/dev-php/smarty/smarty-3.1.31.ebuild
+++ /dev/null
@@ -1,46 +0,0 @@
-# Copyright 1999-2018 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-DOC_PV="3.1.14"
-
-DESCRIPTION="A template engine for PHP"
-HOMEPAGE="https://www.smarty.net/"
-SRC_URI="https://github.com/smarty-php/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz
-	doc? ( https://www.smarty.net/files/docs/manual-en.${DOC_PV}.zip )"
-
-LICENSE="LGPL-3"
-SLOT="0"
-KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
-IUSE="doc"
-
-DEPEND="doc? ( app-arch/unzip )"
-
-# PHP unicode support is detected at runtime, and the cached templates
-# that smarty generates depend on it. If, later on, PHP is reinstalled
-# without unicode support, all of the previously-generated cached
-# templates will begin to throw 500 errrors for missing mb_foo
-# functions. See bug #532618.
-RDEPEND="dev-lang/php:*[unicode]"
-
-src_install() {
-	insinto "/usr/share/php/${PN}"
-	doins -r libs/*
-
-	local DOCS=( *.txt README README.md )
-	local HTML_DOCS
-	use doc && HTML_DOCS="${WORKDIR}/manual-en/"*
-	einstalldocs
-}
-
-pkg_postinst() {
-	elog "${PN} has been installed in /usr/share/php/${PN}/."
-	elog
-	elog 'To use it in your scripts, include the Smarty.class.php file'
-	elog "from the \"${PN}\" directory; for example,"
-	elog
-	elog "  require('${PN}/Smarty.class.php');"
-	elog
-	elog 'After that, the Smarty class will be available to you.'
-}

diff --git a/dev-php/smarty/smarty-3.1.32.ebuild b/dev-php/smarty/smarty-3.1.32.ebuild
deleted file mode 100644
index c1b265f15ea..00000000000
--- a/dev-php/smarty/smarty-3.1.32.ebuild
+++ /dev/null
@@ -1,46 +0,0 @@
-# Copyright 1999-2018 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-DOC_PV="3.1.14"
-
-DESCRIPTION="A template engine for PHP"
-HOMEPAGE="https://www.smarty.net/"
-SRC_URI="https://github.com/smarty-php/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz
-	doc? ( https://www.smarty.net/files/docs/manual-en.${DOC_PV}.zip )"
-
-LICENSE="LGPL-3"
-SLOT="0"
-KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
-IUSE="doc"
-
-DEPEND="doc? ( app-arch/unzip )"
-
-# PHP unicode support is detected at runtime, and the cached templates
-# that smarty generates depend on it. If, later on, PHP is reinstalled
-# without unicode support, all of the previously-generated cached
-# templates will begin to throw 500 errrors for missing mb_foo
-# functions. See bug #532618.
-RDEPEND="dev-lang/php:*[unicode]"
-
-src_install() {
-	insinto "/usr/share/php/${PN}"
-	doins -r libs/*
-
-	local DOCS=( *.txt README README.md )
-	local HTML_DOCS
-	use doc && HTML_DOCS="${WORKDIR}/manual-en/"*
-	einstalldocs
-}
-
-pkg_postinst() {
-	elog "${PN} has been installed in /usr/share/php/${PN}/."
-	elog
-	elog 'To use it in your scripts, include the Smarty.class.php file'
-	elog "from the \"${PN}\" directory; for example,"
-	elog
-	elog "  require('${PN}/Smarty.class.php');"
-	elog
-	elog 'After that, the Smarty class will be available to you.'
-}

next             reply	other threads:[~2019-05-02 22:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 22:40 Michael Orlitzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-11 11:36 [gentoo-commits] repo/gentoo:master commit in: dev-php/smarty/ Arthur Zamarin
2023-12-08 16:29 Arthur Zamarin
2023-05-02 22:49 Michael Orlitzky
2023-05-02 22:49 Michael Orlitzky
2023-04-04  1:36 Michael Orlitzky
2023-01-31 13:41 Michael Orlitzky
2022-09-16 12:38 Michael Orlitzky
2022-09-16 12:38 Michael Orlitzky
2022-09-14 13:17 Michael Orlitzky
2022-05-27 12:43 Michael Orlitzky
2022-05-27 12:43 Michael Orlitzky
2022-05-17 23:29 Michael Orlitzky
2022-02-08 13:24 Brian Evans
2022-02-08  7:22 Agostino Sarubbo
2022-02-07 15:00 Brian Evans
2022-01-11 16:05 Brian Evans
2021-02-24 17:57 Brian Evans
2021-02-24 16:22 Sam James
2021-02-23 14:32 Brian Evans
2021-02-23  3:41 Michael Orlitzky
2020-12-17  3:40 Michael Orlitzky
2020-01-21 23:36 Michael Orlitzky
2019-05-02 21:09 Mikle Kolyada
2019-03-27 23:44 Thomas Deutschmann
2019-03-14 21:14 Agostino Sarubbo
2019-03-11 22:42 Sergei Trofimovich
2019-03-11 19:58 Sergei Trofimovich
2019-03-10 22:17 Sergei Trofimovich
2018-09-17 21:21 Michael Orlitzky
2018-06-07 19:22 Aaron Bauman
2018-05-14 17:47 Brian Evans
2016-12-20 17:42 Brian Evans
2016-11-24  1:52 Michael Orlitzky
2016-11-20 11:39 Aaron Bauman
2016-10-03 18:44 Brian Evans

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:1006772fc4 dfblob:8a87b2c436 dfblob:8d68f8465a
dfblob:c1b265f15e dfblob:c1b265f15e )
 OR (
bs:"[gentoo-commits] repo/gentoo:master commit in: dev-php/smarty/" )
	(help)

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=1556836780.d38cf949be695e971aa9d35dcdeb806eb509469b.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