Date: Tue, 3 Jan 2017 14:53:18 -0500 From: Steve Wills <swills@FreeBSD.org> To: "=?UTF-8?Q?Jos=c3=a9_G._Juanino?=" <jjuanino@gmail.com> Cc: freebsd-ruby@freebsd.org Subject: Re: PREFIX enviroment variable pollutes gem search path Message-ID: <e337a1dc-b541-ae80-e74e-8f34437e830d@FreeBSD.org> In-Reply-To: <20170103192259.c6ebqxy3jwrsgo5o@abel.home.inet> References: <20170103000758.pnoglvxtseec2xpn@abel.home.inet> <20170103142749.62nzduottim5wxpj@abel.home.inet> <5a2c04e1-81bb-41f6-e727-9b4a53682d9b@FreeBSD.org> <20170103192259.c6ebqxy3jwrsgo5o@abel.home.inet>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --FriCTTP2O5dQDLKEdcONv1MS9SshpH424 Content-Type: multipart/mixed; boundary="QcSvJkerT8xQNurkpnOeT1RFBtPGISkjI"; protected-headers="v1" From: Steve Wills <swills@FreeBSD.org> To: =?UTF-8?Q?Jos=c3=a9_G._Juanino?= <jjuanino@gmail.com> Cc: freebsd-ruby@freebsd.org Message-ID: <e337a1dc-b541-ae80-e74e-8f34437e830d@FreeBSD.org> Subject: Re: PREFIX enviroment variable pollutes gem search path References: <20170103000758.pnoglvxtseec2xpn@abel.home.inet> <20170103142749.62nzduottim5wxpj@abel.home.inet> <5a2c04e1-81bb-41f6-e727-9b4a53682d9b@FreeBSD.org> <20170103192259.c6ebqxy3jwrsgo5o@abel.home.inet> In-Reply-To: <20170103192259.c6ebqxy3jwrsgo5o@abel.home.inet> --QcSvJkerT8xQNurkpnOeT1RFBtPGISkjI Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, On 01/03/2017 14:22, Jos=E9 G. Juanino wrote: > Hi Steve, >=20 > 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, an= d > that port requires some other gem, it will fails at the moment it > 'requires' the gem, sure.=20 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 --QcSvJkerT8xQNurkpnOeT1RFBtPGISkjI-- --FriCTTP2O5dQDLKEdcONv1MS9SshpH424 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGQBAEBCgB6BQJYbAEuXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5OEZBNDE0QTVDMkEwRUY5Q0ZEMEFEMERG NUNGNjJCMzIwN0IxQkExExxzd2lsbHNAZnJlZWJzZC5vcmcACgkQ9c9isyB7G6GU Rgf+KT6WCjGM4us1UKEVW7as0f1AHZyu7m0GVK9vwY7BaBFsomXnRp7jpTXzhtTa dNf+KP4bARYXDkzIOKlr80KEJbVpNsNxoHkQIE/3DcI4IGG7xmUn6aLpfI8sZU78 fj2aWuTQTFno3piS++7rJ4PQ1e8GEZbARBPaeWuCCFsi/Q5XfX/AqgwVSd9YndVF oLu8VPhNxD5haPgrbXIAnCsrDCShzr8mD5i2DnRw0K0YaZX19ISyf+ZCN7pHJ1Rg 2ufuJM6uGWK5z+z/cPP9k5uHUahCyAzKGN018gBraKlDBl7mokas8P0nnFCd6LQR O+LTM1uekvz7npJF+qjGpzkj9g== =xtUc -----END PGP SIGNATURE----- --FriCTTP2O5dQDLKEdcONv1MS9SshpH424--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e337a1dc-b541-ae80-e74e-8f34437e830d>