From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <86e7f579a8ed2eb7e874334249dc5b77@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] backwards-incompatible changes 
From: "Russ Cox" <rsc@plan9.bell-labs.com>
In-Reply-To: <200303260143.h2Q1hOt20381@augusta.math.psu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 25 Mar 2003 20:53:04 -0500
Topicbox-Message-UUID: 843766be-eacb-11e9-9e20-41e7f4b1d025

> Ick.  Why not include a /lib/namespace.local, which can do things as it
> sees fit?  The rationale here is that one can keep /lib/namespace the
> same as on sources (reducing the maintenance burden), but provide much
> the same functionality (/lib/namespace.local can include
> /lib/addns.$sysname or something similar).

Because including /lib/namespace.$sysname is a sensible default.
Perhaps /lib/namespace.local should also be included, in the
spirit of /rc/bin/termrc.local and /lib/ndb/local, but that's separate.
If we did it your way, everyone who wanted to use a
/lib/namespace.$sysname would have to create /lib/namespace.local
and maintain that themselves.  I don't see a good reason for it.
You should be able to customize, not be forced to.

Put another way, we use /lib/namespace.$sysname.  Therefore, 
the include of that should go in /lib/namespace (which we can 
tweak) rather than /lib/namespace.local (which is left for you to
tweak).