Problems found locating distfiles:
Package cabocha: missing distfile cabocha-0.68.tar.bz2
Package convertlit: missing distfile clit18src.zip
Package php-enchant: missing distfile php-enchant/enchant-1.1.0.tgz
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.
{perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS
since pkgsrc enforces the newest perl version anyway, so they
should always pick perl, but sometimes (pkg_add) don't due to the
design of the {,} syntax.
No effective change for the above reason.
Ok joerg
Update DEPENDS
Uptream changes:
0.103004 2014-12-26 22:31:16-05:00 America/New_York
- fix a regression in 0.103003, in which Nonpod paragraphs were not
converted into Pod5::Nonpod paragraphs by the Pod5 transformer
0.103003 2014-12-23 21:11:26-05:00 America/New_York
- remove use of Moose::Autobox
0.103002 2014-10-27 21:12:54-04:00 America/New_York
- make classes immutable to improve runtime speed
0.103001 2014-05-20 20:45:43-04:00 America/New_York
- load Class::Load, which older Moose does not automatically load
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
Upstream changes:
0.103000 2014-01-12 09:03:06-05:00 America/New_York
Pod::Elemental::Document only adds leading =pod or trailing =cut if
they are not already present
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
CPAN into textproc/p5-Pod-Elemental.
Pod::Elemental is a system for treating a Pod (plain old documentation)
documents as trees of elements. This model may be familiar from many other
document systems, especially the HTML DOM. Pod::Elemental's document object
model is much less sophisticated than the HTML DOM, but still makes a lot
of document transformations easy.
In general, you'll want to read in a Pod document and then perform a number
of prepackaged transformations on it. The most common of these will be the
Pod5 transformation, which assumes that the basic meaning of Pod commands
described in the Perl 5 documentation hold: =begin, =end, and =for commands
mark regions of the document, leading whitespace marks a verbatim paragraph,
and so on. The Pod5 transformer also eliminates the need to track elements
representing vertical whitespace.
