From: "Brian Evans" <grknight@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-PEAR_PackageFileManager2/
Date: Tue, 27 Dec 2016 16:43:49 +0000 (UTC) [thread overview]
Message-ID: <1482857017.a20c2d2dcaefc197aa317e7402181af1e20a2595.grknight@gentoo> (raw)
commit: a20c2d2dcaefc197aa317e7402181af1e20a2595
Author: Brian Evans <grknight <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 27 16:43:37 2016 +0000
Commit: Brian Evans <grknight <AT> gentoo <DOT> org>
CommitDate: Tue Dec 27 16:43:37 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a20c2d2d
dev-php/PEAR-PEAR_PackageFileManager2: Remove unnecessary src_prepare
It is causing warnings on install and doesn't need to be there
Package-Manager: Portage-2.3.3, Repoman-2.3.1
.../PEAR-PEAR_PackageFileManager2-1.0.4.ebuild | 5 -----
1 file changed, 5 deletions(-)
diff --git a/dev-php/PEAR-PEAR_PackageFileManager2/PEAR-PEAR_PackageFileManager2-1.0.4.ebuild b/dev-php/PEAR-PEAR_PackageFileManager2/PEAR-PEAR_PackageFileManager2-1.0.4.ebuild
index 60d1907..fd369bc 100644
--- a/dev-php/PEAR-PEAR_PackageFileManager2/PEAR-PEAR_PackageFileManager2-1.0.4.ebuild
+++ b/dev-php/PEAR-PEAR_PackageFileManager2/PEAR-PEAR_PackageFileManager2-1.0.4.ebuild
@@ -22,11 +22,6 @@ RDEPEND=">=dev-lang/php-5.3:*
S="${WORKDIR}/${MY_P}"
-src_prepare() {
- default_src_prepare
- sed -i -e '/role="doc"/d' -e '/role="test"/d' "${WORKDIR}/package.xml" || die
-}
-
src_install() {
insinto /usr/share/php
doins -r PEAR
next reply other threads:[~2016-12-27 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 16:43 Brian Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-15 19:16 [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-PEAR_PackageFileManager2/ Brian Evans
2017-03-19 14:52 Brian Evans
2016-12-27 16:43 Brian Evans
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=1482857017.a20c2d2dcaefc197aa317e7402181af1e20a2595.grknight@gentoo \
--to=grknight@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