From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Module-Build/
Date: Sat, 01 Mar 2025 19:38:57 +0000 (UTC) [thread overview]
Message-ID: <1740857690.a546cbe39b5a7c35a51996c35d1570a706d482ed.dilfridge@gentoo> (raw)
commit: a546cbe39b5a7c35a51996c35d1570a706d482ed
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 1 19:34:50 2025 +0000
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sat Mar 1 19:34:50 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a546cbe3
dev-perl/Module-Build: virtual/perl-ExtUtils-Install is going away
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
...Module-Build-0.423.400-r3.ebuild => Module-Build-0.423.400-r4.ebuild} | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-perl/Module-Build/Module-Build-0.423.400-r3.ebuild b/dev-perl/Module-Build/Module-Build-0.423.400-r4.ebuild
similarity index 96%
rename from dev-perl/Module-Build/Module-Build-0.423.400-r3.ebuild
rename to dev-perl/Module-Build/Module-Build-0.423.400-r4.ebuild
index d536a9529187..607d37b5c281 100644
--- a/dev-perl/Module-Build/Module-Build-0.423.400-r3.ebuild
+++ b/dev-perl/Module-Build/Module-Build-0.423.400-r4.ebuild
@@ -16,7 +16,6 @@ RDEPEND="
>=virtual/perl-CPAN-Meta-2.142.60
virtual/perl-Data-Dumper
>=virtual/perl-ExtUtils-CBuilder-0.270.0
- virtual/perl-ExtUtils-Install
virtual/perl-ExtUtils-MakeMaker
>=virtual/perl-ExtUtils-ParseXS-2.210.0
>=virtual/perl-File-Spec-0.820.0
next reply other threads:[~2025-03-01 19:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 19:38 Andreas K. Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-04 20:30 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Module-Build/ Andreas K. Hüttel
2025-03-01 19:33 Andreas K. Hüttel
2025-02-28 21:37 Andreas K. Hüttel
2025-02-28 19:34 Andreas K. Hüttel
2023-08-02 4:27 Sam James
2023-06-20 4:14 Sam James
2022-04-29 7:59 WANG Xuerui
2021-11-14 16:12 Andreas K. Hüttel
2021-08-09 0:54 Sam James
2021-08-07 23:37 Sam James
2021-08-07 14:49 Sam James
2021-08-07 14:49 Sam James
2021-08-07 5:10 Agostino Sarubbo
2021-08-07 1:28 Sam James
2021-08-06 21:18 Sam James
2021-07-04 22:49 Andreas K. Hüttel
2019-05-04 19:02 Andreas K. Hüttel
2018-12-22 10:37 Mikle Kolyada
2018-12-08 15:22 Mikle Kolyada
2018-08-20 3:45 Mikle Kolyada
2018-07-23 19:00 Sergei Trofimovich
2018-07-23 0:43 Mikle Kolyada
2018-07-21 11:50 Tobias Klausmann
2018-07-20 23:18 Sergei Trofimovich
2018-07-20 22:48 Sergei Trofimovich
2018-07-20 8:08 Sergei Trofimovich
2018-07-16 6:54 Sergei Trofimovich
2018-07-15 18:55 Thomas Deutschmann
2018-07-15 15:51 Mikle Kolyada
2018-07-15 10:11 Mart Raudsepp
2017-05-31 23:27 Kent Fredric
2017-04-07 14:05 Kent Fredric
2017-04-03 21:26 Michael Weber
2017-04-03 5:53 Kent Fredric
2017-03-17 11:12 Michael Haubenwallner
2017-02-14 22:52 Michael Weber
2017-02-03 22:27 Jeroen Roovers
2016-09-19 23:15 Kent Fredric
2016-08-10 5:05 Kent Fredric
2016-05-26 0:26 Matt Turner
2016-04-03 19:06 Markus Meier
2016-03-27 19:38 Andreas Hüttel
2016-03-27 19:26 Agostino Sarubbo
2016-03-27 19:23 Agostino Sarubbo
2016-03-15 11:28 Agostino Sarubbo
2016-03-15 11:26 Agostino Sarubbo
2016-02-28 10:01 Patrice Clement
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=1740857690.a546cbe39b5a7c35a51996c35d1570a706d482ed.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