From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <46914d2c-437d-406e-a928-123f4d09f9f7@u15g2000prd.googlegroups.com> <93c7f0c907631447ddb00c5d9280f5eb@brasstown.quanstro.net> Date: Sun, 11 Apr 2010 13:42:30 -0400 Message-ID: From: "Devon H. O'Dell" To: ebo@sandien.com, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] 9vx patch to read environment var PLAN9 Topicbox-Message-UUID: feead92c-ead5-11e9-9d60-3106f5b1d025 2010/4/11 EBo : > I thought p9p uses it for the root of the Plan 9 tree? =A0At least that i= s what > the ebuilds imply. =A0Maybe I am using the wrong term for what PLAN9 poin= ts to. That's true, but in the case of 9vx, the tree it points to contains actual plan 9 binaries, whereas p9p binaries are compiled for the host system. Since it is very feasible that someone may run p9p and 9vx on the same machine (I do, for instance), it would be a good idea to not overload the env var. --dho > =A0EBo -- > > > erik quanstrom said: > >> recommend using a different environment variable >> other than PLAN9, since that is taken by p9p to mean >> something else. >> >> - erik >> > > > > -- > > > > >