Test-Harness depends on ExtUtils/MakeMaker/Config.pm, which is only installed with USE=-build.
This also affects perl-core/PodParse and dev-perl/Locale-gettext. This is an issue build a stage3 tarball from ~arch, as otherwise all three pacakges are build before dev-lang/perl is rebuild without USE=build dev-perl/Locale-gettext is part of a circular dependency. dev-perl/Locale-gettext depends on dev-lang/perl depends on sys-libs/db depends on sys-devel/automake depends on sys-apps/help2man depends on dev-perl/Locale-gettext.
(In reply to comment #1) > This is an issue build a stage3 tarball from ~arch, as otherwise all three > pacakges are build before dev-lang/perl is rebuild without USE=build I don't understand what you are doing exactly and why the modules are installed before perl. Can you please explain?
When building a stage3 tarball with metro, with ~amd64. The stage2 tarball has perl installed with USE=build. Then when rebuilding for stage3, with -build, portage decides to build the modules before perl itself, and so they fail due to lack of ExtUtils/MakeMaker/Config.pm
I don't know how metro works, does it use portage? Because this should be fixed by bug 250020 and in >=portage-2.1.6.8. Is some other package depending on Test-Harness? The problem is: If I'd change it, whose build system will freak out next. But it seems to be sane.
It is an issue with portage. I can cause the errors with emerge directly. This issue seems to be subtle. The problem seems to appear only when help2man pulls in Locale-gettext. The problem doesn't seem to manifest with USE=-nls, preventing Locale-gettext being pulled in, or USE=-berkdb which prevents db (and hence automake and help2man) from being pulled in.
Latest testing perl-core/Test-Harness depends on dev-lang/perl[-build]
