From owner-freebsd-ruby@freebsd.org Tue Jan 3 19:23:07 2017 Return-Path: Delivered-To: freebsd-ruby@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AFD5C9D3E1 for ; Tue, 3 Jan 2017 19:23:07 +0000 (UTC) (envelope-from jjuanino@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 945331202; Tue, 3 Jan 2017 19:23:06 +0000 (UTC) (envelope-from jjuanino@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id c85so49848836wmi.1; Tue, 03 Jan 2017 11:23:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=mKO4xoEaRf2pMRW0PwJUMojLJQ0fCtyOhQey8v29zWE=; b=ZFbWnGmoIAla1QLtiuikl6tRB5U22mVKGCQAPgIDX1AFY5/JBF2mgt181+ZyXmTS4w cDl5VtFc4A3X9pDnfrS4Uuw+QX0rNXH0eEC4wyaGAsFbws+JY2Fa+nA02FvZURKPxSr9 0oeewY5vFii9AEfgMl3GPn0Xz/pcJCA6O2t3La/S+yf5cVGt3MEqMu95vneoUbLy209q B1guy7b50ErZbQBdMChZWJYJwk/rtS6kHeUEhbJHjLUQedfz+fChJXXRb+3L33zICBCh XvUeviTsc/ICEZkSK6SYI7/mdM3YfLVv9X4NMTK3P29GcubAr01IJCVm2aSqZpcw6bAL FBLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=mKO4xoEaRf2pMRW0PwJUMojLJQ0fCtyOhQey8v29zWE=; b=ODxTM7iQN6T58rOpacgbsQlf4RJiaYXHub7pPTtwijwPfuDBKn9Zj4X9D8e2ZDqjSJ jhfOdPKdn373DtQTy16UcDzJZRBx6mi10CoNtpYMulKEiU6tYpUVhy/qNpQhbXQmAZJe eWHZ4ssSNHFhU8cXiMwR6DZrmCBEUfTabw4AMzXypYG3VfsqRBxCpJ4C4ENYfGkRt+9n nR4VSRbSP2s5uJ597cZsqQNqeDlzoi8+KgIY7ydTVDGBqOsD0cHsUTUqyjUACs0pvsPL m3MQjyWU+F3YAimEIxXAH/+6vnKlZgfIOM8MCkGiXpZ4tpQc2aifruUT754/T32rodgU XyZQ== X-Gm-Message-State: AIkVDXIWzbN8y6Q44Vvd8JaJz9HQKyeQynkLy88a0OisEBjFnxPUAJa4g33qa2x4QFUVdg== X-Received: by 10.28.15.138 with SMTP id 132mr51138083wmp.41.1483471384641; Tue, 03 Jan 2017 11:23:04 -0800 (PST) Received: from abel.home.inet (79.108.83.135.dyn.user.ono.com. [79.108.83.135]) by smtp.gmail.com with ESMTPSA id f10sm94482767wjl.28.2017.01.03.11.23.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 03 Jan 2017 11:23:04 -0800 (PST) Date: Tue, 3 Jan 2017 20:22:59 +0100 From: =?iso-8859-1?Q?Jos=E9_G=2E?= Juanino To: Steve Wills Cc: freebsd-ruby@freebsd.org Subject: Re: PREFIX enviroment variable pollutes gem search path Message-ID: <20170103192259.c6ebqxy3jwrsgo5o@abel.home.inet> References: <20170103000758.pnoglvxtseec2xpn@abel.home.inet> <20170103142749.62nzduottim5wxpj@abel.home.inet> <5a2c04e1-81bb-41f6-e727-9b4a53682d9b@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="grwawnqjfbkko3v6" Content-Disposition: inline In-Reply-To: <5a2c04e1-81bb-41f6-e727-9b4a53682d9b@FreeBSD.org> X-Operating-System: FreeBSD 11.0-RELEASE-p2 User-Agent: NeoMutt/20161126 (1.7.1) X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2017 19:23:07 -0000 --grwawnqjfbkko3v6 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El martes 03 de enero a las 16:20:07 CET, Steve Wills escribi=F3: > >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=20 *any* ruby dependent port polluted with PREFIX environment variable, and=20 that port requires some other gem, it will fails at the moment it=20 'requires' the gem, sure. To diagnose and debug is very tricky, I=20 certify :P. Regards --=20 Jos=E9 G. Juanino --grwawnqjfbkko3v6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlhr+gMACgkQFOo0zaS9RnKYmQCfUic+cbKTiVPEHODVlJQu2HkJ +1EAoItMdj33/ef/hQ4exE8m7vN19j18 =F4K1 -----END PGP SIGNATURE----- --grwawnqjfbkko3v6--