Date: Tue, 3 Jan 2017 20:22:59 +0100 From: =?iso-8859-1?Q?Jos=E9_G=2E?= Juanino <jjuanino@gmail.com> To: Steve Wills <swills@FreeBSD.org> Cc: freebsd-ruby@freebsd.org Subject: Re: PREFIX enviroment variable pollutes gem search path Message-ID: <20170103192259.c6ebqxy3jwrsgo5o@abel.home.inet> In-Reply-To: <5a2c04e1-81bb-41f6-e727-9b4a53682d9b@FreeBSD.org> References: <20170103000758.pnoglvxtseec2xpn@abel.home.inet> <20170103142749.62nzduottim5wxpj@abel.home.inet> <5a2c04e1-81bb-41f6-e727-9b4a53682d9b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 detail what existing code this breaks and how >specifically it breaks? It may not be necessary and I actually >considered removing it when adding 2.4 recently but I need to understand >it in more detail first (which is why I didn't remove it already). While >this may break things for some, I can imagine others relying on it. Hi Steve, it breaks some custom code; no port is affected, I think. 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. To diagnose and debug is very tricky, I certify :P. Regards -- José G. Juanino [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlhr+gMACgkQFOo0zaS9RnKYmQCfUic+cbKTiVPEHODVlJQu2HkJ +1EAoItMdj33/ef/hQ4exE8m7vN19j18 =F4K1 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170103192259.c6ebqxy3jwrsgo5o>