On 29 March 2014 06:12, Ciaran McCreesh <[email protected]>wrote:
> These look a lot like they're just parameters to an eclass... An
> alternative approach is to make this explicit, rather than having
> zillions of environment variables:
>
Something I'd *like* to be able to do is have eclass specific keys that map
to other ENVVars, for instance, in some python ebuilds, you have keys that
expand to DEPEND, like PYTHON_REQ_USE, which are kinda messy to have
implemented as eclass parameters.
Mostly, because instead of eclass behaviour being simple inheritance or
"make this function available", you're coupling behaviour to the import
time.
namely, something like:
---
inherit perl-module [
runtime.requires = [ "Moose", "HTTP::Tiny" ]
]
---
Seems like it would get messy too fast, especially with being parseable.
---
inherit perl-module
PERL_RUNTIME_REQUIRES=(
"Moose","HTTP::Tiny"
)
---
with a hook in perl-module that expands those to atoms in DEPENDS
would be much more natural, ( and much more flexible ).
--
Kent
