| 1 |
Source: libio-async-perl |
| 2 |
Standards-Version: 4.7.3 |
| 3 |
Maintainer: Debian Perl Group <[email protected]> |
| 4 |
Uploaders: |
| 5 |
gregor herrmann <[email protected]>, |
| 6 |
Florian Schlichting <[email protected]>, |
| 7 |
Section: perl |
| 8 |
Testsuite: autopkgtest-pkg-perl |
| 9 |
Build-Depends: |
| 10 |
debhelper-compat (= 13), |
| 11 |
libmodule-build-perl, |
| 12 |
perl, |
| 13 |
Build-Depends-Indep: |
| 14 |
libfuture-io-perl <!nocheck>, |
| 15 |
libfuture-perl <!nocheck>, |
| 16 |
libio-socket-ip-perl <!nocheck>, |
| 17 |
libmetrics-any-perl <!nocheck>, |
| 18 |
libsereal-perl <!nocheck>, |
| 19 |
libsocket-perl <!nocheck>, |
| 20 |
libstruct-dumb-perl <!nocheck>, |
| 21 |
libtest-future-io-impl-perl (>= 0.17) <!nocheck>, |
| 22 |
libtest-metrics-any-perl <!nocheck>, |
| 23 |
libtest-pod-perl <!nocheck>, |
| 24 |
libtest2-suite-perl (>= 0.000149) <!nocheck>, |
| 25 |
netbase <!nocheck>, |
| 26 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libio-async-perl |
| 27 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libio-async-perl.git |
| 28 |
Homepage: https://metacpan.org/release/IO-Async |
| 29 |
|
| 30 |
Package: libio-async-perl |
| 31 |
Architecture: all |
| 32 |
Depends: |
| 33 |
${misc:Depends}, |
| 34 |
${perl:Depends}, |
| 35 |
libfuture-perl, |
| 36 |
libsocket-perl, |
| 37 |
libstruct-dumb-perl, |
| 38 |
libtest-metrics-any-perl, |
| 39 |
Recommends: |
| 40 |
libasync-mergepoint-perl, |
| 41 |
libfuture-io-perl, |
| 42 |
libio-socket-ip-perl, |
| 43 |
libmetrics-any-perl, |
| 44 |
libsereal-perl, |
| 45 |
libtest2-suite-perl (>= 0.000149), |
| 46 |
Breaks: |
| 47 |
libio-async-loop-epoll-perl (<< 0.23), |
| 48 |
Description: modules for asynchronous event-driven programming |
| 49 |
The IO::Async collection of modules allows programs to be written that |
| 50 |
perform asynchronous filehandle IO operations. |
| 51 |
. |
| 52 |
A typical program using them would consist of a single subclass of |
| 53 |
IO::Async::Loop to act as a container of other objects, which perform the |
| 54 |
actual IO work required by the program. As well as IO handles, the loop also |
| 55 |
supports timers and signal handlers, and includes more higher-level |
| 56 |
functionality built on top of these basic parts. |