Ubuntu
libanyevent-perl package

libanyevent-perl 7.140-2 source package in Ubuntu

Changelog

libanyevent-perl (7.140-2) unstable; urgency=medium

  [ Alex Muntada ]
  * Remove inactive pkg-perl members from Uploaders.

  [ gregor herrmann ]
  * Skip t/66_ioasync_03_child.t during build and autopkgtest as it seems
    to suffer from a race condition. (Closes: #750732)
  * Set PERL_ANYEVENT_LOOP_TESTS=1 for autopkgtest's smoke test like
    during build.
  * Drop lintian override about a spelling error where lintian removed the
    alleged problem.
  * Declare compliance with Debian Policy 4.1.3.
  * Bump debhelper compatibility level to 10.

 -- gregor herrmann <email address hidden>  Fri, 05 Jan 2018 22:08:43 +0100

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
any
Section:
perl
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Bionic release universe perl

Downloads

File Size SHA-256 Checksum
libanyevent-perl_7.140-2.dsc 2.4 KiB a71d9c5726e3a9df02666dc3a8e4f600726fdfa7c6cc30839c17865a4eaa4691
libanyevent-perl_7.140.orig.tar.gz 294.6 KiB 539358d225bad34b4a64f5217f8c2a707b15e3a28c74120c9dd2270c7cca7d2a
libanyevent-perl_7.140-2.debian.tar.xz 11.3 KiB 519c15f6f70515d0b475ddefb26d0a04e2d16f55c0a3be83b356351a3dfce466

No changes file available.

Binary packages built by this source

libanyevent-perl: event loop framework with multiple implementations

 AnyEvent is not an event model itself, it only interfaces to whatever event
 model the main program happens to use, in a pragmatic way. For event models,
 the statement "there can only be one" is a bitter reality: In general, only
 one event loop can be active at the same time in a process. This module
 cannot change this, but it can hide the differences between them.
 .
 The goal of AnyEvent is to offer module authors the ability to do event
 programming (waiting for I/O or timer events) without subscribing to a
 religion, a way of living, and most importantly: without forcing your module
 users into the same thing by forcing them to use the same event model you use.
 .
 During the first call of any watcher-creation method, the module tries to
 detect the currently loaded event loop by probing whether one of the
 following modules is already loaded: EV, AnyEvent::Loop, Event, Glib, Tk,
 Event::Lib, Qt, POE. The first one found is used. If none are detected, the
 module tries to load the first four modules in the order given; but note that
 if EV is not available, the pure-perl AnyEvent::Loop should always work, so
 the other two are not normally tried.