Commit graph

8 commits

Author SHA1 Message Date
asau
e059e7e469 Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. 2012-10-23 17:18:07 +00:00
wiz
8b5d49eb78 Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.
2012-10-03 21:53:53 +00:00
hiramatsu
4c365885ec Update p5-Data-Stream-Bulk to 0.08.
Change from 0.07.
    - Fix new warnings in Moose
2011-11-21 08:45:08 +00:00
obache
3b0f2f4d0e Revision bump after updating perl5 to 5.14.1. 2011-08-14 14:14:40 +00:00
seb
c3f1e700ad Bump the PKGREVISION for all packages which depend directly on perl,
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!
2010-08-21 16:32:42 +00:00
sno
15707ea5a1 Bumping revision of packages which depend direct or indirect on
devel/p5-Class-MOP. A late detected incompible change forced it.
2009-09-24 06:50:10 +00:00
sno
06d263f94e Updating package net/p5-Data-Stream-Bulk from 0.03 to 0.07
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
2009-08-19 19:50:16 +00:00
he
12ea30c7fe Import p5-Data-Stream-Bulk version 0.03.
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.
2009-01-11 13:56:11 +00:00