The current mk/bulk/build.conf-example contains the following lines:

     # Where our pkgsrc is located
     USR_PKGSRC="/usr/pkgsrc"

Are these lines necessary at all? Generally, we don't support pkgsrc 
trees with mixed versions, so why should anyone be allowed (or even 
encouraged) to use a mk/bulk tree together with an unrelated pkgsrc tree?

I suggest that this configuration knob be removed. In addition, all 
USR_PKGSRC variables should be renamed to PKGSRCDIR, as this is the name 
that's commonly in use outside the bulk build framework. The value of 
PKGSRCDIR should then be determined as follows:

     case ${PKGSRCDIR+set} in
     "")     mydir=`dirname "$0"`
             PKGSRCDIR=`cd "${mydir}/../.." && exec pwd`;;
     esac

That is, it defaults to the pkgsrc tree that the build script is in, but 
can be overridden in the environment if needed.

Implementation of this auto-detection involves some tricky details, but 
here I'm only asking if anyone sees a need for this variable to be 
user-settable.

Roland