[ On Friday, December 3, 1999 at 10:05:11 (-0600), Wenchi Liao wrote: ]
> Subject: Re: Ssh install 
>
> Either way, /etc/mk.conf (IIRC) isn't part of the ``standard''
> install.

No it's not, but it should be.  I've done that for my production
builds.  However I think /etc/mk.conf should only define variables used
in /usr/share/mk/*, not anything to do with pkgsrc.

So given the above I've also had it source /usr/pkgsrc/mk/mk.conf, or
/usr/pkgrsc/mk.conf.example too:

.if exists(/usr/pkgsrc/mk/mk.conf)
. include "/usr/pkgsrc/mk/mk.conf"
.elif exists(/usr/pkgsrc/mk/mk.conf.example)
. include "/usr/pkgsrc/mk/mk.conf.example"
.endif

My mk.conf.example is different than the distributed one, which is why I
must include it even if a local pkgsrc/mk/mk.conf doesn't exist.

Of course this should be made more programmable so that /usr/pkgsrc can
be changed to some arbitrary place with a variable such as PKGSRCDIR in
the same way /usr/src can be moved with BSDSRCDIR.

The above .include of $(PKGSRCDIR)/mk/mk.conf should really be done in
/usr/pkgsrc/bsd.pkg.mk too so that all the other non-pkg builds don't
have to include that file.  I'll probably do that the next time I
localise a NetBSD release for myself.

(While we're in this area, how about renaming pkgsrc/mk to pkgsrc/Mk?
I.e. capitalise "Mk" so that it sorts separately from the category
directories.)

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>      <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>