On Thu, 20 Mar 1997, Rob Deker wrote:

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

That's true. However, if we offer `jumbo packages' of popular
programs, as I suggested, I don't want to have to go through the
entire package before I untar it, just to make sure that none of
the dozens of files it drops in /usr/local/whatever are going to
stomp on programmes I've customised. If I do find a copy of ssh in
the package, chance are it's not configured like mine, and I'd have
to move my /usr/local/*/ssh* stuff all out of the way before I
installed it, and then move my /usr/local/*/ssh* stuff back. That's
a lot more work than just deleting /usr/contrib/*/ssh* after I've
unpacked the jumbo package.

cjs

Curt Sampson    cjs@portal.ca		Info at http://www.portal.ca/
Internet Portal Services, Inc.	
Vancouver, BC   (604) 257-9400		De gustibus, aut bene aut nihil.