From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Package-DeprecationManager/
Date: Thu, 22 Jul 2021 17:39:15 +0000 (UTC) [thread overview]
Message-ID: <1626975538.ef810f1bedea0b1a4df59bfccc6bf50c21f31835.dilfridge@gentoo> (raw)
commit: ef810f1bedea0b1a4df59bfccc6bf50c21f31835
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 22 16:38:30 2021 +0000
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Thu Jul 22 17:38:58 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ef810f1b
dev-perl/Package-DeprecationManager: EAPI=8 bump
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
...-0.170.0.ebuild => Package-DeprecationManager-0.170.0-r1.ebuild} | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/dev-perl/Package-DeprecationManager/Package-DeprecationManager-0.170.0.ebuild b/dev-perl/Package-DeprecationManager/Package-DeprecationManager-0.170.0-r1.ebuild
similarity index 92%
rename from dev-perl/Package-DeprecationManager/Package-DeprecationManager-0.170.0.ebuild
rename to dev-perl/Package-DeprecationManager/Package-DeprecationManager-0.170.0-r1.ebuild
index b38f7dbeb45..2624644bd5f 100644
--- a/dev-perl/Package-DeprecationManager/Package-DeprecationManager-0.170.0.ebuild
+++ b/dev-perl/Package-DeprecationManager/Package-DeprecationManager-0.170.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=DROLSKY
DIST_VERSION=0.17
@@ -12,8 +12,6 @@ DESCRIPTION="Manage deprecation warnings for your distribution"
LICENSE="Artistic-2"
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 ~x86-solaris"
-IUSE="test"
-RESTRICT="!test? ( test )"
RDEPEND="
virtual/perl-Carp
@@ -23,7 +21,7 @@ RDEPEND="
dev-perl/Sub-Install
dev-perl/Sub-Name
"
-DEPEND="${RDEPEND}
+BDEPEND="${RDEPEND}
virtual/perl-ExtUtils-MakeMaker
test? (
virtual/perl-Exporter
next reply other threads:[~2021-07-22 17:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 17:39 Andreas K. Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 23:02 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Package-DeprecationManager/ Sam James
2023-07-24 4:12 Sam James
2023-07-24 4:12 Sam James
2023-07-24 4:02 Sam James
2023-06-20 1:00 Sam James
2020-07-20 20:45 Kent Fredric
2020-04-15 13:46 Kent Fredric
2019-07-28 17:16 Aaron Bauman
2019-07-22 13:58 Mikle Kolyada
2018-10-16 19:02 Fabian Groffen
2018-10-02 7:33 Sergei Trofimovich
2018-09-01 19:01 Thomas Deutschmann
2018-08-30 4:44 Markus Meier
2018-08-20 4:40 Matt Turner
2018-07-27 7:12 Sergei Trofimovich
2018-07-27 7:08 Sergei Trofimovich
2018-07-24 0:12 Mikle Kolyada
2017-01-29 16:45 Fabian Groffen
2016-08-07 7:46 Kent Fredric
2016-08-07 7:46 Kent Fredric
2016-05-26 0:45 Matt Turner
2016-05-21 23:53 Andreas Hüttel
2016-05-21 23:53 Andreas Hüttel
2016-04-26 17:32 Markus Meier
2016-04-10 6:14 Fabian Groffen
2016-04-09 22:54 Andreas Hüttel
2016-01-01 21:32 Andreas Hüttel
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=1626975538.ef810f1bedea0b1a4df59bfccc6bf50c21f31835.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