"Simon J. Gerraty" sez:
/*
 * >I don't see the advantage of keeping every last bit of package-related
 * >stuff under /usr/pkg, except for people developing package stuff
 * 
 * I think I tend to agree.  I was pleased when I saw the recent
 * apache pkg stuff announced - until I read the extent to which the
 * config etc had been frobbed - ....
 * 
 * I can understand wanting all the pkgsrc under one tree, but why
 * _must_ everything be installed under /usr/pkg ?

You mustn't, necessarily.  Use /etc/mk.conf to define LOCALBASE
forcibly to be /usr/local, /usr/foo, or /usr/gofsckyourself [pardon
my Siberian!], and .../pkgsrc/mk/bsd.pkg.mk will install it there
instead.

/etc/mk.conf is a _really_ nice file.

And all the .mk files are recommended reading, at _least_ once.
They provide a deeper insight as to why stuff goes where it does
when you deign not to care.  Just take my word for it -- if you
do care where stuff goes, make the effort to tell the system
you care where it goes, and chances are your system will listen
to you. :-)

 * Its not like any of this stuff can be installed by anyone but
 * root, and if NetBSD itself is ever broken up into pkgs I don't
 * expect to see them installed under /usr/pkg :-)

No, in that case, they probably wouldn't install under ${LOCALBASE}
but probably ${ROOT} or some such, by the time NetBSD itself gets
broken up into pkgs -- something I really wouldn't mind, BTW.

For the record: ${PREFIX}/etc and (no-prefix) /var make more sense than
the other way around.  I have quite a few etc directories (including
a personal one in ~), while I have only one var directory (/var).

{/,*/}etc files are mostly static while /var files change, i.e. _vary_
(I assume that's why they called it /var).

 * --sjg
 */




This conversation is getting interesting.  Has everyone finished
Solstice shopping _already_? :-)



				--*greywolf;
--
"Come, or we shall be late."  "Late for what?"  "What is your name?"  "Dent.
Arthur Dent."  "Late, as in 'the late Dentarthurdent'."