CVS log for pkgsrc/www/p5-Corona/Attic/Makefile

Up to [cvs.NetBSD.org] / pkgsrc / www / p5-Corona

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

Remove p5-Coro and packages depending on it.

Upstream says that it "can not" work with perl 5.22 and has even
forked perl as "stableperl" to allow his package to work instead
of fixing it differently.

See http://blog.schmorp.de/2015-06-06-stableperl-faq.html

Ok bsiegert@

Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.

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.

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.

Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.

Revision bump after updating perl5 to 5.14.1.

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!

Initial import of p5-Net-Server-Coro version 0.8 in the NetBSD
Packages Collection.

The Perl 5 module Net::Server::Coro implements multithreaded server
for the Net::Server architecture, using Coro and Coro::Socket to
make all reads and writes non-blocking. Additionally, it supports
non-blocking SSL negotiation.

Initial revision