On 23 June 2014 07:10, Kent Fredric <kentfred...@gmail.com> wrote: > I'd probably go with PERL_C_BINDINGS=yes or PERL_XS=yes or similar. > > Because there's probably other things that we can infer from that property > and use for other things. > > > And its reasonably straight forward to automatically identify things that > do use XS/C bindings once they're installed, .... just impossible to do in > advance, and difficult to do heuristically during src_configure or similar. > > qfile $( find /usr/lib/perl5 -name "*.so" ) | cut -f 1 -d " " | sort -u >
Actually, that said, its probably wise we don't use PERL_ as a prefix, there's far too much liklihood we'll collide with something in toolchain. Or if we do, make sure we delete that value from %ENV before doing anything with perl. For an example of something we could use GENTOO_PERL_XS=yes for is potentially exposing a tooling feature that indicates whether or not to build the C bits at all. For instance, ExtUtils::MakeMaker responds to the variable PUREPERL_ONLY=1 ( Don't ask me where, I don't know, its really poorly documented ) and Module::Build responds to a parameter --pureperl_only ( badly documented here: https://metacpan.org/pod/distribution/Module-Build/lib/Module/Build/API.pod#allow_pureperl ) ( I'm not saying we should do this, or do this yet, or do this on its own, but it kinda works as justification for the generalist name ) -- Kent
