On 13 December 2015 at 09:41, Andreas K. Huettel <dilfri...@gentoo.org> wrote:
> Well. We had that idea already, and at some point something barfed, I dont
> remember the details anymore. Maybe someone else from the team knows.
>
> The problem is introducing too many variables that look like something
> *upstream* might use...
>
> (We in addition already had creative variable clashes with the kernel module
> build system in the past.)
>
> "Gentoo Perl" would lead to GPL_... as variable prefix, not really suitable.
> Kent suggested GPLX_... which I find horrible. GPERL_? GP_? ...
Yeah. There's a bit of a potential issue with using the PERL_ prefix
in that that prefix is heavily overloaded /in perl/ things, and `perl
-V` subsequently reports all ENV vars with a PERL prefix ( underscore
or not )
PERL_MOM=Yours perl -V | grep MOM
PERL_MOM="Yours"
So using the PERL_ prefix increases our chances we'll pick something
that will collide, or will mislead somebody into thinking that we're
using an ENV var that Perl reacts magically to, where the ENV var is
purely Gentoo and Purely part of our private API ( At least, its
supposed to be private from the context of a perl interpreter )
If there was a way to mark those vars so they didn't get exported to
perl that would help, but it wouldn't reduce the "What does this do"
impression-confusion.
--
Kent
KENTNL - https://metacpan.org/author/KENTNL
