Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
and ${CFLAGS}. This fixes the build of net/djbdns, as well as any
other of these packages passing down PKG_SYSCONFDIR via CFLAGS, as
well as being more generally correct for arbitrary user-defined
CFLAGS. Suggested by jlam.
For consistency across djbware in pkgsrc:
* In math/djbfft's and sysutils/daemontools's do-configure targets,
remove leading @ from ${ECHO} lines; from the former, also remove
unneeded single quotes from one such line.
* Rename net/publicfile's pre-build and sysutils/service-config's
post-patch targets to do-configure.
* In sysutils/checkpassword's do-configure target, reorder creation
of conf-cc, conf-ld, and conf-home.
All of the affected packages have been verified to compile.
XXX These packages probably have enough build goo in common to
XXX warrant an mk/djbware.mk. I'll investigate this post-freeze.
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
The programs in service-config create and configure svscan-format
service directories.
* server-config creates an svscan-format directory for an arbitrary
service.
* rules-config configures access rules for use by a
service.
* svscan-config configures a service to run svscan.
* ipc-config configures a service to run ipcserver.
* ipcx-config configures a service to run ipcserver using access
rules.
* tcp-config configures a service to run tcpserver.
* tcpx-config configures a service to run tcpserver using access
rules.
