On Wed, 22 Nov 2000, Frederick Bruckman wrote:

: > Not if the line reads MKCRYPTO=no instead of MKCRYPTO?=no.  The difference
: > is very important to bsd.pkg.mk, which does recursion and does not pass down
: > "overrides".
: 
: For settings in the environment, yes. But do you have an explanation
: for the following? It looks as if setting a variable on the command
: line (and /etc/mk.conf simultaneously) produces undefined behavior...

It's not undefined.  Reread:

    ...bsd.pkg.mk, which does recursion and does not pass down "overrides".

: root@handy-> make MKCRYPTO=yes
: ===> vnc-3.3.3.1 may not be built, because it utilizes strong cryptography
: => Checksum OK for vnc-3.3.3r1_unixsrc.tgz.
: => Checksum mismatch for vnc-latest_doc.tgz.
: Make sure the Makefile and md5 file (/s/pkgsrc/net/vnc/files/md5)
: are up to date.  If you want to override this check, type
: "make NO_CHECKSUM=yes [other args]".
: *** Error code 1
: 
: Stop.
: root@handy-> MKCRYPTO=yes make
: ===> vnc-3.3.3.1 may not be built, because it utilizes strong cryptography
: root@handy-> 

This is because you're overriding in the topmost make, which will then try
to do something, but the recursion won't see the override.

The best way to interpret this is "if you set it in mk.conf absolutely,
don't expect it to be overridable on pkgs."

-- 
-- Todd Vierling <tv@wasabisystems.com>  *  http://www.wasabisystems.com/
-- Speed, stability, security, and support.  Wasabi NetBSD:  Run with it.