Source: libpoe-component-client-ping-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: gregor herrmann <gregoa@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper-compat (= 13)
Build-Depends-Indep: libpoe-perl <!nocheck>,
                     perl
Standards-Version: 4.5.1
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libpoe-component-client-ping-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libpoe-component-client-ping-perl.git
Homepage: https://metacpan.org/release/POE-Component-Client-Ping
Rules-Requires-Root: no

Package: libpoe-component-client-ping-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libpoe-perl
Description: ICMP ping client component for POE
 POE::Component::Client::Ping is an asynchronous, event driven client
 for ICMP ping. It accepts events containing the specifics of ICMP
 ping requests, and it returns events carrying the results of those
 pings.
 .
 Ping client components are not proper objects.  Instead of being
 created, as most objects are, they are "spawned" as separate sessions.
 To avoid confusion (and hopefully not cause other confusion), they
 must be spawned with a spawn method, not created anew with a new
 one.