Commit graph

12 commits

Author SHA1 Message Date
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
obache
a1a10a43f3 Update p5-Coro to 6.31.
Revision history for Perl extension Coro.

6.31 Thu May  9 07:39:48 CEST 2013
	- Coro::AIO requests would crash if the thread was ready'd
          while the request was ongoing.

6.29 Wed May  8 02:55:18 CEST 2013
	- when an on_destroy handler destructs the coro currently being
          destructed a perl scalar could be accessed after being freed,
          likely causing a crash.

6.28 Wed Mar  6 06:58:02 CET 2013
	- clean remnants of existing __DIE__ and __WARN__ handlers so
          they lose their magic and will not cause segfaults later
          (testcase by Andrey Sagulin).
	- improved Coro::State documentation a bit.
        - Coro::Debug::command now flushes the output.
        - add hack detection code for x32 abi, because the braindead slugs
          who designed that made it look exactly like x86_64 without
          providing proper compile time symbols to test for it. as a result,
          this detection cannot work reliably.
        - valgrind stack registering was broken.
        - do not rely on Time::HiRes anymore in Coro::Debug.

6.23 Fri Dec  7 23:36:37 CET 2012
        - use experimental fiber implementation on native windows
          perls.
        - use sizeof (void *) as multiplication factor for stack sizes,
          to accomodate the totally braindamaged microsoft 64 bit "os".
        - changed verifier host from win2k-ap510-32 to win7-sp516-32/64.
          activeperl 5.16 crashes when PerlIO_define_layer is called due
          to some bug in the perl dll, strawberry perl at least passes
          the testsuite.
        - implement Coro::Handle->peeraddr/host/port, for slightly
          improved compatibility with LWP.
	- implement 5.17 compatibility by almost blindly applying a
          good-looking patch by Father Chrysostomos.
        - move stack management functions into libcoro 3.
        - libcoro version 3 "released".
	- support magic values as timed_io_once args.
	- recommend AnyEvent 7+ or EV 4+, also require EV
          version 4 or newer for Coro::EV.

6.10 Tue Oct  9 01:14:27 CEST 2012
	- updated ecb.h, it had a typo that caused it to not compile on many
          big endian systems (reported by many people).
        - disable memory fences in ecb.h to improve portability.

6.09 Sat Oct  6 23:25:02 CEST 2012
	- Coro::EV I/O watchers were not interruptible by exceptions
          (Coro::State::throw) (testcase by sten).
        - ->throw now puts threads into the ready queue, as this seems to
          be expected by existing code, and code that doesn't cope with spurious
          wakeups needs fixing anyway.
	- use fd -1 in mmap.
        - cast I32 to int in error message printf.
        - warn about broken so-called "hardened" kernels.

6.08 Fri Apr 13 12:05:47 CEST 2012
	- be more aggressive about exiting like perl does - formerly,
          exiting from the non-main thread would not execute END blocks.
2013-09-02 13:16:26 +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
e1ab7079b6 Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. 2012-10-31 11:16:30 +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
d001a00079 Update p5-Coro to 6.07.
Changes from previous:
----------------------
6.07 Fri Nov 11 21:21:48 CET 2011
	- work around a bug in PerlIO (setting $SIG{__WARN__} to a PVCV).
        - update ecb.h.
2011-12-09 02:08:56 +00:00
hiramatsu
947d29b186 Updated to recent release to fix build problem with perl 5.14. 2011-09-13 05:24:07 +00:00
obache
39619a9444 Revision bump after updating perl5 to 5.14.1. 2011-08-14 12:26:04 +00:00
hiramatsu
093f6ae412 Updated to 5.25. This fixes build problem due to API changes of devel/libev.
5.25  Thu Nov 11 01:08:39 CET 2010
        - try a different approach on netbsd - netbsd 5 finally has marginally
          working pthreads, but still broken ucontext/sigaltstack.
        - openbsd 4.8 finally got their act together, Coro works out of the box
          with asm, setjmp and pthreads (no change, just informational).

5.24  Sat Oct 23 11:27:12 CEST 2010
        - port to the EV 4.0 API.
        - work around bugs in mingw32, making strawberry perl work
          out of the box.
        - correctly modify Coro::AIO function prototypes
          so that they reflect the "no optional parameters" rule.
        - "ported" libcoro to C++.
2010-12-17 02:22:36 +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
seb
1a1393e227 Update p5-Coro from version 5.22 to version 5.23.
Upstream changes:
5.23  Mon May 17 18:50:42 CEST 2010
	- be more resistant to ordering changes when initialising
          Coro::AnyEvent, Coro::EV and Coro::Event (reported by Matthias
          Waldorf).
	- document that perl 5.12 deliberately removed support for cloning.
2010-05-24 20:53:31 +00:00
seb
e2d46a95d8 Initial import of p5-Coro version 5.22 in the NetBSD Packages
Collection.

The Perl 5 module collection Coro manages continuations in general,
most often in the form of cooperative threads.The specific flavor
of thread offered by this module also guarantees you that it will
not switch between threads unless necessary, at easily-identified
points in your program, so locking and parallel access are rarely
an issue, making thread programming much safer and easier than using
other thread models.
2010-04-19 22:11:50 +00:00