Linux workstation

Upstream software project

php-pear

PHP Extension and Application Repository framework

About php-pear

PHP Extension and Application Repository framework

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

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.php-pear: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
php-pear
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
BSD-2-Clause AND BSD-3-Clause AND LGPL-3.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.

PEAR is a framework and distribution system for reusable PHP components. This package contains the basic PEAR components.

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.

Fedora 43

  1. php-pear

    Fedora 43 / Unspecified / source php-pear

    1:1.10.17-1.fc43

    PHP Extension and Application Repository framework

    noarch43

Fedora 44

  1. php-pear

    Fedora 44 / Unspecified / source php-pear

    1:1.10.18-2.fc44

    PHP Extension and Application Repository framework

    noarch44

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.