developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
It is more consistent with the tex.buildlink3.mk name. Also, if a package
really needs latex, it just has to set TEX_ACCEPTED to latex distributions
altough today, all TEX_ACCEPTED possibilities are latex distributions
needed to install the module. Packages that require plugins from the
Template Toolkit should depend on modules needed to make those plugins
function. Bump the PKGREVISION of p5-Template-Toolkit to 3.
For the packages that depend directly on p5-Template-Toolkit, add as
dependencies all of the packages needed to make the plugins work to
the package Makefiles, and bump their PKGREVISIONs.
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").
binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.
addresses PR pkg/28619 from H. Todd Fujinaka.
template extraction functionality. It can take a rendered document
and its template together, and get the original data structure
back, effectively reversing the "process" function.
This module is considered experimental. If you just wish to extract
RSS-type information out of a HTML document, WWW::SherlockSearch
may be a more robust solution.