Log message:
Avoid finding pkgsrc-installed bash, as it won't be in the sandbox. Bump
PKGREVISION.

Log message:
pkgtools: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Log message:
parallel: Remove SHA1 hashes for distfiles

Log message:
Update pkg_comp to 2.1:

Changes in version 2.1
======================

**Released on 2019-01-14.**

* Issue 3: Added a new `PBULK_LOG` setting to point at a location that
  holds all build logs, and made the `build` command print out details
  about such logs on success and failure.

* Issue 4: Fixed the installable bootstrap kit generated during a build
  to not leak pkg_comp-internal paths.

* Issue 10: Fixed generation of pkg_summary so that it includes all
  packages and not only those that were explicitly given to the `auto`
  or `build` commands after a clean rebuild of the sandbox.

* PR 20: Fixed the default Git repository from jsonn's to NetBSD's as
  it has moved upstream.

* Added a new `PKG_DEVELOPER` setting to enable pkgsrc development
  from within the sandbox.

Log message:
Fix typo in reference to pkgbuild-user.

Problem found by Ian D. Leroux and reported via private email... a few
months ago.  My bad.

Log message:
pkgtools/pkg_comp: Correct usage of ${PKG_SYSCONFDIR}.

Package configuration files should be found in ${PKG_SYSCONFDIR},
which can be modified by a user-settable variable.  Look for the
default sandboxctl(8) configuration files in
${PKG_SYSCONFDIR.sandboxctl} if that variable is set, or else in
${PKG_SYSCONFBASE}/sandboxctl.

Fixes problem noted by Iain Hibbert on tech-pkg@.

Bump the PKGREVISION to 2 due to changes in the binary package if
PKG_SYSCONFDIR.pkg_comp is set to a non-default value.

Log message:
Fix sysconfdir settings for pkg_comp.

This allows the default configuration in pkg_comp to properly find the
default configuration of sandboxctl.

Bump PKGREVISION to 1.

Log message:
Hardcode the location of sandboxctl to not rely on the PATH.

Should fix the problems observed in:
http://ftp.netbsd.org/pub/pkgsrc/misc/joerg/20170219.1406/meta/report.html

Log message:
Readd pkg_comp, now at version 2.0:

**Released on 2017-02-17.**

This is the first release of the pkg_comp project as a standalone
package.  This new release shares no code with previous versions and is
not compatible with them.

The following are the major differences between pkg_comp 2.0 and all
previous releases, which incidentally are the reasons that triggered
this rewrite:

* Support for multiple platforms.

* Use of pbulk to (re)build packages within the sandbox.  This results
  in more reliable incremental builds after pkgsrc updates.

* Support for bootstrap, generating binary kits as part of the builds.

* Better scriptability to allow running from cron(8) trivially.

Log message:
Update pkg_comp to 1.38nb1

pkgsrc uses the "BUILD_TARGET" definition internally as the primary
target for building in a package's WRKDIR.  It defaults to "all".
So pkgsrc cd's to ${WRKDIR} and does a "make ${BUILD_TARGET}"

pkg_comp also wants to use the same "BUILD_TARGET" definition
internally for itself to guide the builds for making binary packages.
It's done at a higher level than the pkgsrc definition.  It defaults
to "package".

The use of the same name for two different purposes can cause
pkg_comp to fail to build packages. This commit renames the pkg_comp
definition to be "BUILD_PKG_COMP_TARGET".

With this change in place, my pkg_comp builds now complete successfully.

Bump PKGREVISION for the BUILD_PKG_COMP_TARGET fix