| 1 |
Source: libio-pipely-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: Florian Schlichting <[email protected]> |
| 4 |
Section: perl |
| 5 |
Testsuite: autopkgtest-pkg-perl |
| 6 |
Priority: optional |
| 7 |
Build-Depends: debhelper-compat (= 13) |
| 8 |
Build-Depends-Indep: perl |
| 9 |
Standards-Version: 4.6.0 |
| 10 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libio-pipely-perl |
| 11 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libio-pipely-perl.git |
| 12 |
Homepage: https://metacpan.org/release/IO-Pipely |
| 13 |
Rules-Requires-Root: no |
| 14 |
|
| 15 |
Package: libio-pipely-perl |
| 16 |
Architecture: all |
| 17 |
Depends: ${misc:Depends}, |
| 18 |
${perl:Depends} |
| 19 |
Description: portable way to create pipe() or pipe-like handles |
| 20 |
IO::Pipely provides a couple functions to portably create one- and |
| 21 |
two-way pipes and pipe-like socket pairs. It acknowledges and works |
| 22 |
around known platform issues so you don't have to. |
| 23 |
. |
| 24 |
IO::Pipely currently understands pipe(), UNIX-domain socketpair() and |
| 25 |
regular IPv4 localhost sockets. It will use different kinds of pipes or |
| 26 |
sockets depending on the operating system's capabilities and the number |
| 27 |
of directions requested. The autodetection may be overridden by |
| 28 |
specifying a particular pipe type. |
| 29 |
. |
| 30 |
IO::Pipely is a spin-off of the POE project's portable pipes. Earlier |
| 31 |
versions of the code have been tested and used in production systems for |
| 32 |
over a decade. |