By setting EAPI=5, the ebuild triggers stricter handling of IUSE, causing errors like this: WARNING: One or more updates have been skipped due to a dependency conflict: dev-lang/perl:0 (dev-lang/perl-5.16.2::gentoo, ebuild scheduled for merge) conflicts with dev-lang/perl[-build] required by (dev-perl/Net-HTTP-6.30.0::gentoo, installed) (dev-lang/perl-5.16.2::gentoo, ebuild scheduled for merge) conflicts with dev-lang/perl[-build] required by (dev-perl/Encode-Locale-1.30.0::gentoo, installed) (dev-lang/perl-5.16.2::gentoo, ebuild scheduled for merge) conflicts with dev-lang/perl[-build] required by (perl-core/IO-1.25::gentoo, installed) (dev-lang/perl-5.16.2::gentoo, ebuild scheduled for merge) conflicts with dev-lang/perl[-build] required by (dev-util/App-SVN-Bisect-1.1::gentoo, installed) Possible resolutions are: 1. Add build to IUSE in dev-lang/perl-5.16.2 2. Change the dependency to "dev-lang/perl[-build(-)]" in perl-module.eclass and upgrade all perl modules to EAPI >= 4 3. Downgrade perl-5.16.2 to EAPI 4 temporarily
4. Add "build" (and maybe "bootstrap" for consistency) to IUSE_IMPLICIT variable in gentoo-x86/profiles/base/make.defaults.
I am tempted to choose a) add "build" to perl-5.16.2 and remove it once the older ebuilds are gone. But I cannot fix it right now. If anyone wants to, just do it.
I choose option 1 and just moved it to my local overlay. Worked like a champ. defaults to disabled anyway (-build)
Created attachment 336302 [details] fixed ebuild
(In reply to comment #2) Sounds good to me. Committed.
It's unclear to me how to exactly resolve the problem. I've synced the new ebuild but when I try to emerge it with the build flag all my perl modules complain, for example, dev-lang/perl[-build] required by (dev-perl/libxml-perl-0.80.0::gentoo, installed) Is there a workaround for this?
"build" is only used in early stage building. Do emerge dev-lang/perl with USE="-build".