Summary: | perl-modules.eclass updates/fixes | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel Robbins (RETIRED) <drobbins> |
Component: | [OLD] Core system | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED LATER | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Robbins (RETIRED)
2003-10-19 14:25:13 UTC
Note: perl-module.eclass would override any existing functions that are conditional on USE=perl with ones that will always run. The idea seems good but I think we need some naming schema foreclass. We have "elisp-common.eclass" that "elisp.eclass" inherits(we split these ebuilds just the same reason you are going to dofor perl). Also, we have "common-lisp-common.eclass" (who named it?)that "common-lisp.eclass" imports some functions from. Given theseeclass names I think "perl-common.eclass" would be better than "perl-utils.eclass" because you would think *-common.eclass is the eclassyou may use when you don't want all the DEPEND/RDEPEND. I think this needs to wait until eclasses are rearchitected in portage-ng. |