PREFIX enviroment variable pollutes gem search path

[Steve Wills]

Hi,

On 01/03/2017 14:22, José G. Juanino wrote:
> Hi Steve,
> 
> it breaks some custom code; no port is affected, I think.

Ok, good to know.

> But if you run
> *any* ruby dependent port polluted with PREFIX environment variable, and
> that port requires some other gem, it will fails at the moment it
> 'requires' the gem, sure. 

Describing it as "polluted" with a PREFIX environment variable seems a
bit inaccurate to me. PREFIX is a commonly used variable on FreeBSD and
in this case it's mean to indicate to gem where it might find some
things. I'm guessing your custom code checks for this variable as well
and also is meant to use it for something else? Perhaps it could be
change to use a different variable name?

> To diagnose and debug is very tricky, I
> certify :P.

Yeah, I can imagine that was confusing. :)

Steve

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 632 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ruby/attachments/20170103/bb49bb1f/attachment.sig>