From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 12 Apr 2010 05:38:54 -0600 To: "Francisco J Ballesteros" , "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> From: "EBo" Message-ID: In-Reply-To: References: <46914d2c-437d-406e-a928-123f4d09f9f7@u15g2000prd.googlegroups.com> <94f361d12533ee74d9af4827460b357b@ladd.quanstro.net> , Subject: Re: [9fans] 9vx patch to read environment var PLAN9 Topicbox-Message-UUID: ff6d2e04-ead5-11e9-9d60-3106f5b1d025 Francisco J Ballesteros said: > you could also use a script to call 9vx as you please. That is what I did for the first prototype. I thought this would be a beeter solution. Out of curiosity, have I hit a nerve or something. Have I somehow offended? I'm just a bit confused by some of the responses. I could easily understand the reluctance if there are some standardization issues with getenv on the targeted platforms I do not know about. I could also understand if I was proposing to put it in some weird location, but both of the hard-coded paths in 9vx main.c are obviously in RSC's home directories and not more generic locations like /home/9vx, $home/9vx, /usr/local/9vx, /opt... EBo -- > On Mon, Apr 12, 2010 at 5:22 AM, EBo wrote: > > > >> Why isn't 9vx -r yourdir good enough? > > > > it is if you want to force all users to specify the root directory every > > single time they run 9vx, or if you want to use an alternative root.  If I use > > a standard install locations then we can either change "/Users/rsc/9vx" and > > "/home/rsc/plan9/4e" or I can simply run a sed script during the build phase. > >  Setting up a $root9vx (what I have changed it to) seemed the cleanest approach. > > > >  EBo --