From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/cvsps/
Date: Sun, 10 Nov 2019 11:59:52 +0000 (UTC) [thread overview]
Message-ID: <1573387185.26c9933a73f18482bf3a4ef04f07b2f2ce1f7708.slyfox@gentoo> (raw)
commit: 26c9933a73f18482bf3a4ef04f07b2f2ce1f7708
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 10 11:59:35 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Nov 10 11:59:45 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=26c9933a
dev-vcs/cvsps: refresh up to EAPI=7
Package-Manager: Portage-2.3.79, Repoman-2.3.18
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-vcs/cvsps/{cvsps-3.13-r1.ebuild => cvsps-3.13-r2.ebuild} | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/dev-vcs/cvsps/cvsps-3.13-r1.ebuild b/dev-vcs/cvsps/cvsps-3.13-r2.ebuild
similarity index 90%
rename from dev-vcs/cvsps/cvsps-3.13-r1.ebuild
rename to dev-vcs/cvsps/cvsps-3.13-r2.ebuild
index 45e63d4b5dc..1d9ca2cea5f 100644
--- a/dev-vcs/cvsps/cvsps-3.13-r1.ebuild
+++ b/dev-vcs/cvsps/cvsps-3.13-r2.ebuild
@@ -1,7 +1,7 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
-EAPI=5
+EAPI=7
inherit eutils toolchain-funcs
@@ -20,10 +20,13 @@ DEPEND="${RDEPEND}
RESTRICT=test # upstream does not ship tests
+PATCHES=("${FILESDIR}"/${P}-make.patch)
+
src_prepare() {
+ default
+
local gentoo_name=${PN}-3
- epatch "${FILESDIR}"/${P}-make.patch
mv ${PN}.asc ${gentoo_name}.asc || die
sed -i "s/${PN}/${gentoo_name}/g" ${gentoo_name}.asc || die
sed -i "s/PROG = cvsps/PROG = ${gentoo_name}/" Makefile || die
@@ -34,5 +37,6 @@ src_prepare() {
src_install() {
default
+
dodoc README
}
next reply other threads:[~2019-11-10 11:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 11:59 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-12 6:12 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/cvsps/ WANG Xuerui
2022-05-01 1:52 WANG Xuerui
2021-09-28 12:44 James Le Cuirot
2021-09-28 12:39 James Le Cuirot
2021-07-21 11:05 Marek Szuba
2021-07-20 23:18 Marek Szuba
2021-07-02 7:17 Sergei Trofimovich
2021-01-06 22:58 Fabian Groffen
2020-06-16 22:02 Andreas Sturmlechner
2020-06-08 16:34 Mart Raudsepp
2020-05-25 21:33 Sergei Trofimovich
2020-05-21 8:06 Agostino Sarubbo
2020-05-21 8:03 Agostino Sarubbo
2020-05-21 8:02 Agostino Sarubbo
2020-05-21 8:00 Agostino Sarubbo
2020-05-21 7:58 Agostino Sarubbo
2020-05-21 7:57 Agostino Sarubbo
2020-05-21 7:53 Agostino Sarubbo
2020-03-31 17:51 Mart Raudsepp
2020-02-13 13:03 Agostino Sarubbo
2020-02-12 19:57 Sergei Trofimovich
2020-02-11 11:30 Agostino Sarubbo
2020-02-11 11:09 Agostino Sarubbo
2020-02-11 10:58 Agostino Sarubbo
2020-02-11 10:55 Agostino Sarubbo
2020-02-11 9:52 Agostino Sarubbo
2020-02-11 9:43 Agostino Sarubbo
2020-02-10 18:10 Agostino Sarubbo
2019-12-09 20:20 Sergei Trofimovich
2019-11-10 9:19 Michał Górny
2019-10-11 22:32 Sergei Trofimovich
2019-10-07 19:12 Sergei Trofimovich
2019-10-07 10:38 Agostino Sarubbo
2019-10-07 8:59 Agostino Sarubbo
2019-10-07 7:29 Agostino Sarubbo
2017-08-14 6:37 Michał Górny
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=1573387185.26c9933a73f18482bf3a4ef04f07b2f2ce1f7708.slyfox@gentoo \
--to=slyfox@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