File: control

package info (click to toggle)
libanyevent-perl 7.010-1
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 1,528 kB
  • sloc: perl: 6,349; sh: 108; makefile: 10
file content (54 lines) | stat: -rw-r--r-- 1,899 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
Source: libanyevent-perl
Section: perl
Priority: optional
Build-Depends: debhelper (>= 9.20120312), perl,
 libasync-interrupt-perl,
 libev-perl,
 libevent-perl,
 libglib-perl,
 libio-async-perl,
 libnet-ssleay-perl,
 libpoe-perl,
 perl-tk,
 netbase,
 shared-mime-info,
 xauth,
 xvfb
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Jonathan Yu <jawnsy@cpan.org>,
 Ansgar Burchardt <ansgar@debian.org>,
 gregor herrmann <gregoa@debian.org>,
 Maximilian Gass <mxey@cloudconnected.org>,
 Nicholas Bamber <nicholas@periapt.co.uk>,
 Alessandro Ghedini <ghedo@debian.org>
Standards-Version: 3.9.3
Homepage: http://search.cpan.org/dist/AnyEvent/
Vcs-Git: git://git.debian.org/pkg-perl/packages/libanyevent-perl.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libanyevent-perl.git

Package: libanyevent-perl
Architecture: any
Depends: ${perl:Depends}, ${misc:Depends}
Suggests: libasync-interrupt-perl,
 libev-perl,
 libevent-perl,
 libglib-perl,
 libguard-perl,
 libio-async-perl,
 libjson-perl (>= 2.09) | libjson-xs-perl (>= 2.220),
 libnet-ssleay-perl,
 libpoe-perl,
 libtask-weaken-perl,
 perl-tk
Description: 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.