From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Unicode-UTF8/
Date: Sat, 2 Oct 2021 00:13:37 +0000 (UTC) [thread overview]
Message-ID: <1633133591.11e38ead1d0221a1d432dbff5c7ba21ec5159f29.dilfridge@gentoo> (raw)
commit: 11e38ead1d0221a1d432dbff5c7ba21ec5159f29
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 2 00:05:31 2021 +0000
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sat Oct 2 00:13:11 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=11e38ead
dev-perl/Unicode-UTF8: EAPI=8 bump
Package-Manager: Portage-3.0.26, Repoman-3.0.3
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
...{Unicode-UTF8-0.620.0.ebuild => Unicode-UTF8-0.620.0-r1.ebuild} | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/dev-perl/Unicode-UTF8/Unicode-UTF8-0.620.0.ebuild b/dev-perl/Unicode-UTF8/Unicode-UTF8-0.620.0-r1.ebuild
similarity index 92%
rename from dev-perl/Unicode-UTF8/Unicode-UTF8-0.620.0.ebuild
rename to dev-perl/Unicode-UTF8/Unicode-UTF8-0.620.0-r1.ebuild
index fff638d52f7..a476fc5f986 100644
--- a/dev-perl/Unicode-UTF8/Unicode-UTF8-0.620.0.ebuild
+++ b/dev-perl/Unicode-UTF8/Unicode-UTF8-0.620.0-r1.ebuild
@@ -1,7 +1,7 @@
# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
-EAPI=6
+EAPI=8
DIST_AUTHOR=CHANSEN
DIST_VERSION=0.62
@@ -11,15 +11,13 @@ DESCRIPTION="Encoding and decoding of UTF-8 encoding form"
SLOT="0"
KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
-IUSE="test"
-RESTRICT="!test? ( test )"
RDEPEND="
virtual/perl-Carp
virtual/perl-Exporter
virtual/perl-XSLoader
"
-DEPEND="${RDEPEND}
+BDEPEND="${RDEPEND}
>=virtual/perl-ExtUtils-MakeMaker-6.590.0
test? (
>=virtual/perl-Encode-1.980.100
@@ -31,6 +29,7 @@ DEPEND="${RDEPEND}
dev-perl/Test-LeakTrace
)
"
+
src_test() {
perl_rm_files t/999_pod.t
perl-module_src_test
next reply other threads:[~2021-10-02 0:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 0:13 Andreas K. Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-14 6:54 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Unicode-UTF8/ WANG Xuerui
2020-12-27 16:19 Fabian Groffen
2019-07-19 7:49 Mikle Kolyada
2019-01-29 13:31 Mikle Kolyada
2019-01-17 20:39 Mikle Kolyada
2018-10-27 12:45 Fabian Groffen
2018-10-11 14:56 Andreas Hüttel
2018-10-06 19:34 Matt Turner
2018-10-02 7:33 Sergei Trofimovich
2018-09-30 18:52 Sergei Trofimovich
2018-08-20 4:40 Matt Turner
2018-08-04 0:29 Mikle Kolyada
2018-04-15 21:10 Sergei Trofimovich
2018-03-28 4:09 Matt Turner
2018-03-01 14:28 Michał Górny
2017-07-07 7:33 Alexis Ballier
2017-05-31 2:51 Kent Fredric
2017-05-22 1:19 Michael Weber
2017-05-20 9:34 Agostino Sarubbo
2017-05-20 8:49 Agostino Sarubbo
2017-04-12 15:10 Kent Fredric
2017-04-12 15:09 Kent Fredric
2017-04-11 20:03 Kent Fredric
2016-08-06 11:54 Kent Fredric
2016-07-08 20:37 Andreas Hüttel
2016-05-25 23:08 Matt Turner
2016-03-15 12:13 Agostino Sarubbo
2016-03-15 12:11 Agostino Sarubbo
2016-03-15 12:10 Agostino Sarubbo
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=1633133591.11e38ead1d0221a1d432dbff5c7ba21ec5159f29.dilfridge@gentoo \
--to=dilfridge@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