Locale-gettext-1.01-r1.ebuild and Locale-gettext-1.03.ebuild
contain only DEPEND="sys-devel/gettext" lines.
These ebuilds do, in fact, depend on dev-lang/perl and this
should be reflected in the DEPEND line.
Attempting to emerge Locale-gettext-1.01-r1 or
Locale-gettext-1.03 without perl installed fails with an
error stating the command "perl" cannot be found.
You need to read the ebuilds better (hint: inherit), not to mention the fact the perl is part of system target.
(In reply to comment #1)
> You need to read the ebuilds better (hint: inherit), not to mention the fact
I assume, then, that ebuilds inherit the DEPEND from their parent class...
I didn't know it happened that way.
> the perl is part of system target.
That's exactly the problem. I don't *have* a system, yet. I just bootstrapped,
and Locale-gettext is trying to use perl before it's been merged. If a
dependency on perl is inherited from perl-module, why isn't portage pulling in
perl (its dependency) before Locale-gettext? I'd assumed it was because
"dev-lang/perl" was missing from the Locale-gettext DEPEND. So what's causing
How did you get a base system without perl? (its part of the stage3 tarball - are you doing a stage1?)
As noted in Bug 122488 and Bug 122489, you are using stage 1/2 in an incorrect way. You need 'emerge --emptytree system', not emerge system.
(In reply to comment #4)
> As noted in Bug 122488 and Bug 122489, you are using stage 1/2 in an incorrect
> way. You need 'emerge --emptytree system', not emerge system.
In case anyone searches and comes across this report, I was using "emerge
-e system" (and yes, after bootstrapping stage 1 to stage 2). This one
purely is a purely wetware bug: I didn't read the perl-module eclass.