Andreas K. Huettel posted on Sun, 22 Jun 2014 20:13:59 +0200 as excerpted: > Offhand I don't know any way how the eclass could "know" whether a perl > package requires C building or not. Any heuristics would be a hack at > best. It might even be preferable to manually add some variable to 300 > packages in the ebuild (which then makes the eclass add a use-flag > custom-cflags). > i.e. > > PERL_CFLAGS_HANDLING=yes inherit perl-module
Namespace collision issues aside, that would have been my next suggestion, yes. The kde eclasses among others make extended use of this sort of "pre-inherit or pre-eclass-function-call declaration" solution. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
