Version 5.1, 2016-07-06
* Globbing patterns in #include statement
If argument to the #include statement contains wildcard characters (*, [,
], or ?), it is interpreted as shell globbing pattern and all files
matching that pattern are included, in lexicographical order. If no
matching files are found, the directive is replaced with an empty
line.
* New watcher option 'shell'
The 'shell' option causes watcher command to be executed via
'/bin/sh' (by default it is invoked directly, using the 'execve'
function). For example:
watcher {
path "/etc/httpd/vhosts";
command "/usr/bin/scanhosts && service httpd restart";
option (shell);
}
* Include path
If the argument to the #include (#include_once) statement is not an
absolute file name or globbing pattern, it is looked up in the include
search path. The order of look up is as follows. First, directories
given with '-I' options (see below) are scanned, in the same order as
given on the command line. If no matching file is found in any of
them, directories in the standard include search path are scanned.
By default, the standard include search path contains two directories:
'$(pkgdatadir)/$(VERSION)' and '$(pkgdatadir)/include', where
$(pkgdatadir) and $(VERSION) stand for the package data directory, and
package version, correspondingly. It can be redefined at compile time using
the '--with-include-path' to configure, e.g.:
./configure --with-include-path='$(sysconfdir)/direvent.d:$(pkgdatadir)/$(VERSION):$(pkgdatadir)/include'
(see the file INSTALL, section "Building and Configuring", for a
detailed discussion of this option).
To inspect the actual path at runtime, run 'direvent --help',
and look for the string 'Include search path:' in its output.
* New command line option -I (--include)
The '-I DIR' command line option adds DIR to the include search path.
When looking for include files, directories given with '-I' options
are scanned first. If the file is not found, the directories in the
standard include path are scanned.
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.
Direvent is a directory content watcher daemon, i.e. a program that
monitors a set of directories on the file system and reacts when
their content changes. When a change is detected, the daemon reacts by
invoking an external command configured for that kind of change.
The program aims to provide a uniform and system-independent
command-level interface for file system events.
