9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] backwards-incompatible changes
Date: Tue, 25 Mar 2003 20:53:04 -0500	[thread overview]
Message-ID: <86e7f579a8ed2eb7e874334249dc5b77@plan9.bell-labs.com> (raw)
In-Reply-To: <200303260143.h2Q1hOt20381@augusta.math.psu.edu>

> 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).




  reply	other threads:[~2003-03-26  1:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 21:58 Russ Cox
2003-03-26  1:43 ` Dan Cross
2003-03-26  1:53   ` Russ Cox [this message]
2003-03-26  2:09     ` Dan Cross
2003-03-26  2:20       ` Russ Cox
2003-03-26  2:34       ` Geoff Collyer
2003-03-26  1:35 Russ Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86e7f579a8ed2eb7e874334249dc5b77@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).