Upstream software project

perl-log-any

Bringing loggers and listeners together

About perl-log-any

Bringing loggers and listeners together

This project links 12 native package records across 9 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

Alpine Linux 3.21: 2 package records; Alpine Linux 3.22: 2 package records; Alpine Linux 3.23: 2 package records; Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.perl-log-any: recorded package coverageAlpine Linux 3.212 recordsAlpine Linux 3.222 recordsAlpine Linux 3.232 recordsDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 16.01 records
OpenFactory diagram of linked package records. The first eight releases are shown; all 9 appear below. It is not an application screenshot.

Project identity

Project
perl-log-any
Publisher
Not authoritatively mapped
Native package records
12
Operating systems
alpine-linux-3-21, alpine-linux-3-22, alpine-linux-3-23, debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-1.0-or-later OR Artistic-1.0-Perl
Source repository
Not reported

Source-reported description

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

'Log::Any' provides a standard log production API for modules. Log::Any::Adapter allows applications to choose the mechanism for log consumption, whether screen, file or another logging mechanism like Log::Dispatch or Log::Log4perl. Many modules have something interesting to say. Unfortunately there is no standard way for them to say it - some output to STDERR, others to 'warn', others to custom file logs. And there is no standard way to get a module to start talking - sometimes you must call a uniquely named method, other times set a package variable. This being Perl, there are many logging mechanisms available on CPAN. Each has their pros and cons. Unfortunately, the existence of so many mechanisms makes it difficult for a CPAN author to commit his/her users to one of them. This may be why many CPAN modules invent their own logging or choose not to log at all. To untangle this situation, we must separate the two parts of a logging API. The first, _log production_, includes methods to output logs (like '$log->debug') and methods to inspect whether a log level is activated (like '$log->is_debug'). This is generally all that CPAN modules care about. The second, _log consumption_, includes a way to configure where logging goes (a file, the screen, etc.) and the code to send it there. This choice generally belongs to the application. A CPAN module uses 'Log::Any' to get a log producer object. An application, in turn, may choose one or more logging mechanisms via Log::Any::Adapter, or none at all. 'Log::Any' has a very tiny footprint and no dependencies beyond Perl 5.8.1, which makes it appropriate for even small CPAN modules to use. It defaults to 'null' logging activity, so a module can safely log without worrying about whether the application has chosen (or will ever choose) a logging mechanism. See http://www.openswartz.com/2007/09/06/standard-logging-api/ for the original post proposing this module.

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.

Alpine Linux 3.21

  1. Package perl-log-any

    v3.21 (Alpine Linux 3.21): Bringing loggers and listeners together

    1.717-r0: aarch64 x86_64

    Source: perl-log-any

  2. Package perl-log-any-doc

    v3.21 (Alpine Linux 3.21): Bringing loggers and listeners together (documentation)

    1.717-r0: aarch64 x86_64

    Source: perl-log-any

Alpine Linux 3.22

  1. Package perl-log-any

    v3.22 (Alpine Linux 3.22): Bringing loggers and listeners together

    1.717-r0: aarch64 x86_64

    Source: perl-log-any

  2. Package perl-log-any-doc

    v3.22 (Alpine Linux 3.22): Bringing loggers and listeners together (documentation)

    1.717-r0: aarch64 x86_64

    Source: perl-log-any

Alpine Linux 3.23

  1. Package perl-log-any

    v3.23 (Alpine Linux 3.23): Bringing loggers and listeners together

    1.718-r0: aarch64 x86_64

    Source: perl-log-any

  2. Package perl-log-any-doc

    v3.23 (Alpine Linux 3.23): Bringing loggers and listeners together (documentation)

    1.718-r0: aarch64 x86_64

    Source: perl-log-any

Debian 12 (Bookworm)

  1. Package liblog-any-perl

    bookworm (Debian 12 (Bookworm)) (perl): Perl module to log messages safely and efficiently

    1.713-1: all

Debian 13 (Trixie)

  1. Package liblog-any-perl

    trixie (Debian 13 (Trixie)) (perl): Perl module to log messages safely and efficiently

    1.717-1: all

Fedora 43

  1. Package perl-Log-Any

    43 (Fedora 43) (Unspecified): Bringing loggers and listeners together

    1.718-1.fc43: noarch

    Source: perl-Log-Any

Fedora 44

  1. Package perl-Log-Any

    44 (Fedora 44) (Unspecified): Bringing loggers and listeners together

    1.718-2.fc44: noarch

    Source: perl-Log-Any

openSUSE Leap 16.0

  1. Package perl-Log-Any

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Bringing loggers and listeners together

    1.717.0-bp160.1.12: noarch

    Source: perl-Log-Any

openSUSE Tumbleweed

  1. Package perl-Log-Any

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Bringing loggers and listeners together

    1.720.0-1.3: noarch

    Source: perl-Log-Any

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.