On Wed, 19 Mar 1997, Curt Sampson wrote:

> I'd say they go in /usr/contrib, just as BSDi does it. In fact, it
> would make a lot of sense to have a contrib13.tar.gz kit with our
> next release that would contain a pile of the most frequently asked
> for binaries (perl, ssh, emacs, apache, etc.). That would go a
> long way toward making NetBSD more palatable to those who just want
> to `load and go,' without polluting either the standard directories
> or /usr/local.
> 
I wouldn't say that using /usr/local/ would "pollute" anything. By my
way of thinking /usr/local is for installation of site-specific packages.
If people are picking and choosing packages for a site, that in itself is
site-specificity. and we wouldn't have to "pollute" search paths and the
like by adding /usr/contrib/BLAH on top of /usr/local/BLAH...

...but this is starting to sound like the kind of bickering that will
kill something like this. So, let's stop. If you have strong feelings
about this kind of stuff and want to help in being "constructive" about
it, send me some mail, I'll set up a mailing list or something...

rob



------------------------------------------------------------------------------
"Off the keyboard, through the CPU, | deker@digex.net 
out the transceiver, down the rj45  | Systems Engineer
line, across the router, through    | 
the Hub, out the gateway.           |  
        Nothing but net."           | 
-----------------------------------------------------------------------------