Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 122428

Summary: Locale-gettext ebuilds missing a dependency (dev-lang/perl)
Product: Gentoo Linux Reporter: kevin asher <virginsnow>
Component: New packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: VERIFIED INVALID    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description kevin asher 2006-02-10 21:23:25 UTC
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.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-02-11 00:50:43 UTC
You need to read the ebuilds better (hint: inherit), not to mention the fact the perl is part of system target.
Comment 2 kevin asher 2006-02-11 07:59:32 UTC
(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
this then?
Comment 3 Michael Cummings (RETIRED) gentoo-dev 2006-02-11 08:36:14 UTC
How did you get a base system without perl? (its part of the stage3 tarball - are you doing a stage1?)
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2006-02-11 11:44:35 UTC
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.

Closing.
Comment 5 kevin asher 2006-03-26 13:45:31 UTC
(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.

> Closing.
Agreed.