Linux workstation

Upstream software project

libio-pipely-perl

Portably create pipe() or pipe-like handles, one way or another

About libio-pipely-perl

Portably create pipe() or pipe-like handles, one way or another

This project links 6 native package records across 6 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.libio-pipely-perl: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libio-pipely-perl
Publisher
Not authoritatively mapped
Native package records
6
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-tumbleweed
License expression
Artistic-1.0 OR GPL-1.0-or-later
Metadata completeness
100/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Pipes are troublesome beasts because there are a few different, incompatible ways to create them. Not all platforms support all ways, and some platforms may have hidden difficulties like incomplete or buggy support. IO::Pipely provides a couple functions to portably create one- and two-way pipes and pipe-like socket pairs. It acknowledges and works around known platform issues so you don't have to. On the other hand, it doesn't work around unknown issues, so please report any problems early and often. IO::Pipely currently understands pipe(), UNIX-domain socketpair() and regular IPv4 localhost sockets. This covers every platform tested so far, but it's hardly complete. Please help support other mechanisms, such as INET-domain socketpair() and IPv6 localhost sockets. IO::Pipely will use different kinds of pipes or sockets depending on the operating system's capabilities and the number of directions requested. The autodetection may be overridden by specifying a particular pipe type.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. libio-pipely-perl

    Debian 12 (Bookworm) / perl

    0.006-1

    portable way to create pipe() or pipe-like handles

    allbookworm

Debian 13 (Trixie)

  1. libio-pipely-perl

    Debian 13 (Trixie) / perl

    0.006-1

    portable way to create pipe() or pipe-like handles

    alltrixie

Fedora 43

  1. perl-IO-Pipely

    Fedora 43 / Unspecified / source perl-IO-Pipely

    0.006-10.fc43

    Portably create pipe() or pipe-like handles, one way or another

    noarch43

Fedora 44

  1. perl-IO-Pipely

    Fedora 44 / Unspecified / source perl-IO-Pipely

    0.006-11.fc44

    Portably create pipe() or pipe-like handles, one way or another

    noarch44

openSUSE Leap 15.6

  1. perl-IO-Pipely

    openSUSE Leap 15.6 / Unspecified / source perl-IO-Pipely

    0.006-bp156.2.1

    Portably create pipe() or pipe-like handles, one way or another

    noarchleap-15.6

openSUSE Tumbleweed

  1. perl-IO-Pipely

    openSUSE Tumbleweed / Unspecified / source perl-IO-Pipely

    0.6.0-1.5

    Portably create pipe() or pipe-like handles, one way or another

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.