Upstream software project

cpanspec

RPM spec file generation utility

About cpanspec

RPM spec file generation utility

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.cpanspec: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
cpanspec
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
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.

cpanspec generates spec files (and, optionally, source or even binary packages) for Perl modules from CPAN for Fedora. The quality of the spec file is our primary concern. It is assumed that maintainers will need to do some (hopefully small) amount of work to clean up the generated spec file to make the package build and to verify that all of the information contained in the spec file is correct.

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. Package cpanspec

    43 (Fedora 43) (Unspecified): RPM spec file generation utility

    1.78-55.fc43: noarch

    Source: cpanspec

Fedora 44

  1. Package cpanspec

    44 (Fedora 44) (Unspecified): RPM spec file generation utility

    1.78-57.fc44: noarch

    Source: cpanspec

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.