Commit graph

16 commits

Author SHA1 Message Date
maya
649096cd51 Fix build with perl 5.26 2017-06-12 08:06:25 +00:00
ryoon
b9d9d2fc30 Recursive revbump from lang/perl5 5.26.0 2017-06-05 14:24:48 +00:00
wiz
86a78fce2e Bump PKGREVISION for perl-5.24. 2016-06-08 19:22:13 +00:00
agc
b9b754e081 Add SHA512 digests for distfiles for www category
Problems found locating distfiles:
	Package haskell-cgi: missing distfile haskell-cgi-20001206.tar.gz
	Package nginx: missing distfile array-var-nginx-module-0.04.tar.gz
	Package nginx: missing distfile encrypted-session-nginx-module-0.04.tar.gz
	Package nginx: missing distfile headers-more-nginx-module-0.261.tar.gz
	Package nginx: missing distfile nginx_http_push_module-0.692.tar.gz
	Package nginx: missing distfile set-misc-nginx-module-0.29.tar.gz
	Package nginx-devel: missing distfile echo-nginx-module-0.58.tar.gz
	Package nginx-devel: missing distfile form-input-nginx-module-0.11.tar.gz
	Package nginx-devel: missing distfile lua-nginx-module-0.9.16.tar.gz
	Package nginx-devel: missing distfile nginx_http_push_module-0.692.tar.gz
	Package nginx-devel: missing distfile set-misc-nginx-module-0.29.tar.gz
	Package php-owncloud: missing distfile owncloud-8.2.0.tar.bz2

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.
2015-11-04 02:46:46 +00:00
wiz
2e65d464e8 Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.
2015-06-12 10:50:58 +00:00
wiz
7eeb51b534 Bump for perl-5.20.0.
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.
2014-05-29 23:35:13 +00:00
wen
28aad9c09c Update to 0.96
Upstream changes:
0.96    2011-11-27
        - fix test failure

0.95    2011-11-20
        - switch Class::Data::Accessor to Catalyst::ClassData
        - address rt #68997 "log levels too high" ticket
2013-08-23 13:59:19 +00:00
wiz
d2ca14a3f1 Bump all packages for perl-5.18, that
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.
2013-05-31 12:39:57 +00:00
asau
5eae6a18a3 Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. 2012-10-28 06:30:00 +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
7f87114339 Update p5-Catalyst-Plugin-AutoRestart to 0.94.
Change from previous:
0.94    2011-06-29
                - Add option to kill through HUP signal instead of exit.
2011-11-05 20:25:52 +00:00
obache
84fa8bcd7c Revision bump after updating perl5 to 5.14.1. 2011-08-14 16:05:39 +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
4026a1061b Updating www/p5-Catalyst-Plugin-AutoRestart from 0.92nb1 to 0.93
pkgsrc changes:
- Adding license definition
- Adjust dependencies
- Apply correct module type

Upstream changes:
0.93	2010-01-29
	- Changing Class::C3 to MRO::Compat
2010-02-02 11:28:01 +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
abs
8f9d00bea2 Added www/p5-Catalyst-Plugin-AutoRestart version 0.92
Catalyst plugin to force the application to restart server processes
when they reach a configurable memory threshold. Memory checks are
performed every 'N' requests. This is intended as a band-aid to
deal with problems like memory leaks; it's here to buy you time to
find and solve the underlying issues.
2008-10-31 11:50:42 +00:00