From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Wed, 14 Apr 2010 13:01:37 -0600
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>,
	"Skip Tavakkolian" <9nut@9netics.com>
From: "EBo" <ebo@sandien.com>
Message-ID: <twig.1271271697.97703@swcp.com>
In-Reply-To: <2a13f4556b5b2430836b81136e5ba71f@9netics.com>
References: <twig.1271268649.33455@swcp.com>
Subject: Re: [9fans] 9vx patch to read environment var PLAN9
Topicbox-Message-UUID: 01508752-ead6-11e9-9d60-3106f5b1d025


> the point is that any default is bound to be wrong.  my guess is that
> '/home/rsc/...' default was introduced early in the development and
> before '-r' was added.  it might be more useful to lobby for a default
> location like '/usr/lib/9vx'.
>
> secondly writing
>
> $ NINEROOT=/usr/ebo/9vxroot 9vx
>
> is less pleasant than:
>
> $ 9vx -r /usr/ebo/9vxroot
>
> it's true that NINEROOT can be set and forgotten about, but the same
> argument could be made for writing a shell function that aliases 9vx
> to '9vx -r ...' etc -- and probably in the same place, e.g. .profile.

excellent, some constructive feedback, and thank all of you who have done so.

We already have -r so that we can either alias 9vx, or write a two line
wrapper as also previously suggested.

Now lets debate if there should be any hard coded paths in the program.  Where
are the most appropraite locations?  We could of course open up the /opt
/usr/local debate again, but there is also putting it into /usr/share/9vx and
/usr/lib/9vx as suggested. We could hash out what is suggested with the Linux
Standard Base, or throw the whole thing out the window.

What I have decided to do for my current work is to put it in /usr/local.
Why?  I am working on Tvx, and their standard install is in /usr/local/${package}

I'll take consensus on the NINEROOT and ${home}/ if people do not mind that
complexity.

  EBo --