What's this

pkgchkxx and pkgrrxx are complete rewrites of pkgsrc pkg_chk and pkg_rolling-replace respectively. These are functionally compatible but run faster:

• pkgrrxx -u runs roughly N times faster than pkg_rolling-replace -u where N is the number of CPUs you have.
• pkgrrxx -sn runs 14.8x faster than pkg_rolling-replace -sn.
• pkgchkxx -aur -b runs 11x faster than pkg_chk -aur -b when pkg_summary(5) file is available.
• pkgchkxx -aur -s runs 3x faster than pkg_chk -aur -s.
• pkgchkxx -l runs 185x faster than pkg_chk -l when pkg_summary(5) file is available, and runs 24.8x faster when it's unavailable (and needs to scan archives).
• pkgchkxx -p runs 1.3x faster than pkg_chk -p.
• pkgchkxx -g runs 1.6x faster than pkg_chk -g.
• pkgchkxx -N runs 22x faster than pkg_chk -N.

This implementation achieves better performance by using a faster language, better algorithms, and making use of more than a single CPU whenever possible. The last one is the primary reason why a complete rewrite was needed: doing it in POSIX shell was simply not feasible.

External dependencies

• A C++17 compiler. For GCC it has to be GCC 8 or later.
• GNU Make, only needed for building the programs.
• pkg_install, obviously.
• pkg-config for determining what pkg_chk tags to predefine. This is a run-time dependency.
• bzip2 for reading bzip2-compressed pkg_summary(5) files.
• zlib for reading gzip-compressed pkg_summary(5) files.
• libfetch for fetching pkg_summary(5) files from a remote host.

Release notes

See NEWS.

Building and installation

% ./configure
% gmake
% sudo gmake install

You may need to give ./configure the path to your compiler if the system compiler doesn't support C++17:

% ./configure CXX=/path/to/cxx

Hacking

See HACKING.

License

BSD-2-Clause AND BSD-3-Clause. See COPYING.

Author

The NetBSD Foundation