El martes 03 de enero a las 20:53:18 CET, Steve Wills escribió:
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
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
El martes 03 de enero a las 16:20:07 CET, Steve Wills escribió:
This was added in r210636 (nearly 8 years ago) to "allow modules to be
installed into separate PREFIX and/or under user privilegies" (sic) and
so far I believe this is the first issue I've seen with it.
Can you explain in more
Hi,
On 01/03/2017 09:27, José G. Juanino wrote:
>> In short: you cannot load any gem if your environment contains the
>> PREFIX variable. When this happens, ruby uses the assigned value
>> instead of /usr/local to search the proper files. This breaks a lot of
>> existent code.
>>
>> The relevant
El martes 03 de enero a las 01:07:58 CET, José G. Juanino escribió:
Hi,
I am suffering an annoying issue loading gem libraries; I am not sure
if it is FreeBSD specific.
Install some gem, for example rubygem-test-unit-3.1.9, and take a look
at the following code:
$ ruby22 -r test/unit -e
Hi,
I am suffering an annoying issue loading gem libraries; I am not sure if
it is FreeBSD specific.
Install some gem, for example rubygem-test-unit-3.1.9, and take a look
at the following code:
$ ruby22 -r test/unit -e 'puts'
$ PREFIX=1 ruby22 -r test/unit -ne 'puts'
