CVS log for pkgsrc/devel/p5-Async-Interrupt/Makefile

Up to [NetBSD + pkgsrc-wip] / pkgsrc / devel / p5-Async-Interrupt

Request diff between arbitrary revisions - Display revisions graphically

Keyword substitution: kv
Default branch: MAIN

Revision bump after updating perl 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!

Update p5-Async-Interrupt from version 1.04 to version 1.05.

Pkgsrc changes:
- adjust MASTER_SITES

Upstream changes:
1.05  Sat May 15 02:06:33 CEST 2010
	- implement $epipe->signal_func method.

Update p5-Async-Interrupt from version 1.03 to version 1.04.

Pkgsrc changes:
- placate pkglint

Upstream changes:
1.04  Wed Mar 31 02:46:49 CEST 2010
        - a double fork partially killed the event pipe (great testcase
          by dormando). affects IO::AIO, BDB and Async::Interrupt.

Updating devel/p5-Async-Interrupt from 1.02 to 1.03

pkgsrc changes:
- Add USE_LANGUAGES to mark it's an XS based module requiring a C Compiler

Upstream changes:
1.03  Tue Nov 24 14:31:10 CET 2009
	- port to loser platform.

Updating devel/p5-Async-Interrupt from 1.01 to 1.02

Upstream changes:
1.02  Tue Sep  1 18:41:09 CEST 2009
	- prototypes for sig2name/sig2num were missing.

Importing package for perl5 module Async::Interrupt 1.01 as dependency
for devel/p5-AnyEvent.

This module implements a single feature only of interest to advanced perl
modules, namely asynchronous interruptions (think "UNIX signals", which are
very similar).

Sometimes, modules wish to run code asynchronously (in another thread, or
from a signal handler), and then signal the perl interpreter on certain
events. One common way is to write some data to a pipe and use an event
handling toolkit to watch for I/O events. Another way is to send a signal.
Those methods are slow, and in the case of a pipe, also not asynchronous -
it won't interrupt a running perl interpreter.

This module implements asynchronous notifications that enable you to signal
running perl code from another thread, asynchronously, and sometimes even
without using a single syscall.

Initial revision