All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Not committed (merge conflicts...):
net/radsecproxy/distinfo
The following distfiles could not be fetched (fetched conditionally?):
./net/citrix_ica/distinfo citrix_ica-10.6.115659/en.linuxx86.tar.gz
./net/djbdns/distinfo dnscache-1.05-multiple-ip.patch
./net/djbdns/distinfo djbdns-1.05-test28.diff.xz
./net/djbdns/distinfo djbdns-1.05-ignoreip2.patch
./net/djbdns/distinfo djbdns-1.05-multiip.diff
./net/djbdns/distinfo djbdns-cachestats.patch
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.
Add missing DEPENDS
Upstream changes:
0.11 2012-02-13
- needs to actually depend on Path::Class
0.10 2012-02-12
- Fix ::FileHandle on pre-5.14 perls
0.09 2012-02-12
- oops, missed rafl's upload, rerelease with the correct version number
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.
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
pkgsrc changes:
- Adding license
- Adjusting dependencies
Upstream changes:
0.07
- Fix new warnings in Moose about overwriting methods
0.06
- Fix several pod errors (Closes RT#43490) (Ryan Niebur)
- Add pod tests
- Update version control notice
0.05
- Silence some new warnings from Moose
0.04
- add exclusions to role composition to avoid the new warning
This module tries to find middle ground between one at a time and
all at once processing of data sets.
The purpose of this module is to avoid the overhead of implementing
an iterative api when this isn't necessary, without breaking forward
compatibility in case that becomes necessary later on.
The API optimizes for when a data set typically fits in memory and
is returned as an array, but the consumer cannot assume that the
data set is bounded.
The API is destructive in order to minimize the chance that resultsets
are leaked due to improper usage.
