On 13:08 Mon 02 Mar     , Torsten Veller wrote:
> Currently the eclass doesn't set any dependencies. If it is used the 
> ebuild has to depend on perl if needed.
> 
> 
> I see the following options:
> 
> 1) Don't add DEPEND to the eclass.
>    So if a package is used for stage-building we have to raise EAPI and
>    depend on dev-lang/perl[-build] in the ebuild.
> 
>    The part I don't understand in the bug above is:
>    Does adding dev-lang/perl[-build] automagically reinstall
>    perl during stage-building
>    (here portage stops and complains).
> 
> 
> 2) Add DEPEND conditionally to the eclass.
>    To give ebuilds the chance to inherit perl-module.eclass
>    (and currently also perl-app.eclass) and support perl conditionally,
>    we have to add another global variable to check it.
> 
>    (Checking CATEGORY and perl? probably could be added additonally)
> 
> 
> 3) Add DEPEND.
>    Always depend on dev-lang/perl and 
>    if EAPI=2 then depend on dev-lang/perl[-build]
> 
> 
> Comments?

Having not spent a lot of time thinking about this, I'm guessing the use 
case of concern is packages that have an optional perl module always 
pulling in dev-lang/perl. This would apparently be relevant on an 
embedded system that lacked perl but required a package with an optional 
perl module. To handle that miniscule use case, I'd tend to go with a 
conditional variable (GENTOO_PERL="no"?) that defaults to "yes".

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com