Log message:
Update to 2.6:

- Fix the default configuration file to populate CVSTAG correctly when
  using a CVS/Tag file.
- Ensure that errors from CVS stop execution.

Problem reported by Nathan Arthur in private mail.  Change OKed by pmc.

Log message:
Update to 2.5:

- Added support for pre/post fetch/build hooks so that, for example, rsync
  can be used to push the results of a successful build to a remote server.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
Update to 2.4:

- Add a MKVARS variable to pass arbitrary variables to build.sh through -V.
  E.g. MKVARS="MKDEBUG=yes".
- Move the documentation of the configuration file to a new sysbuild.conf(5).

Log message:
Update to 2.3:

- Added the 'env' command.  This prints a small shell snippet that can be
  imported into the current shell.  The printed code defines a set of
  convenience global variables and functions to work with the source tree.

Log message:
Update to 2.2:

- Add support to specify per-machine targets by prefixing the targets in
  BUILD_TARGETS by the machine they correspond to.  Useful, for example,
  to build different kernels depending on the machine type.

Log message:
Update to 2.1:

- Use shtk for the common utilities and configuration file parsing
  functionality.  The local copies of the "config" and \ 
"utils" modules
  are gone.

Log message:
Use Nx for NetBSD. Add RCS Id. Remove dot at end of SEE ALSO.

Log message:
Minor mdoc fix.

Log message:
Initial (re)addition of sysbuild, version 2.0:

sysbuild is a tool to automate the maintenance of the NetBSD sources and
the build of releases by means of a single command and a configuration
file that tells sysbuild what to do.

Since NetBSD 1.6 (released on July 2011), the source tree has included a
very flexible script (build.sh) to build a full NetBSD release for the
current platform or to cross-build for any of the supported platforms.

The flipside of the flexibility is that the script is inconvenient to use
on a daily basis because of the myriad of options it takes.  Furthermore,
managing the source trees that make up NetBSD is not in the scope of
build.sh: the user must fetch these trees and keep them up to date by hand.

While these details are all fine on their own, rebuilding NetBSD frequently
(to keep a system up to date, or just for development tasks) is convoluted.
Developers and users usually find themselves writing their own wrapper
scripts over build.sh to simplify their daily tasks.

sysbuild extends build.sh by adding support for configuration files and
source tree management, allowing NetBSD rebuilds with a single and simple
command.  Make sure to check the sysbuild-user package for a way to
trivially set up periodic NetBSD rebuilds under an dedicated, unprivileged
user.

This is version 2.0 because sysbuild already existed 10 years ago.  It
served the same purpose, but it was removed because it stopped working
with NetBSD 2.0 (can't remember why though).  Also, I'm convinced the
previous implementation was quite bad.