Upstream software project

perl-CPAN-Changes

Read and write Changes files

About perl-CPAN-Changes

Read and write Changes files

This project links 1 native package record across 1 recorded operating-system release. 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

openSUSE Leap 15.6: 1 package records. Catalog coverage diagram, not an application screenshot.perl-CPAN-Changes: recorded package coverageopenSUSE Leap 15.61 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
perl-CPAN-Changes
Publisher
Not authoritatively mapped
Native package records
1
Operating systems
opensuse-leap-15-6
License expression
Artistic-1.0 or GPL-1.0+
Source repository
Not reported

Source-reported description

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

It is standard practice to include a Changes file in your distribution. The purpose the Changes file is to help a user figure out what has changed since the last release. People have devised many ways to write the Changes file. A preliminary specification has been created (the CPAN::Changes::Spec manpage) to encourage module authors to write clear and concise Changes. This module will help users programmatically read and write Changes files that conform to the specification.

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.

openSUSE Leap 15.6

  1. Package perl-CPAN-Changes

    leap-15.6 (openSUSE Leap 15.6) (Development/Libraries/Perl): Read and write Changes files

    0.400002-1.24: noarch

    Source: perl-CPAN-Changes

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.