Upstream software project

perl-namespace-clean

Keep imports and functions out of your namespace

About perl-namespace-clean

Keep imports and functions out of your namespace

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

openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records. Catalog coverage diagram, not an application screenshot.perl-namespace-clean: recorded package coverageopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
perl-namespace-clean
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-15-6, opensuse-leap-16-0
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.

Keep imports and functions out of your namespace

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-namespace-clean

    leap-15.6 (openSUSE Leap 15.6) (Development/Libraries/Perl): Keep imports and functions out of your namespace

    0.27-1.22: noarch

    Source: perl-namespace-clean

openSUSE Leap 16.0

  1. Package perl-namespace-clean

    leap-16.0 (openSUSE Leap 16.0) (Development/Libraries/Perl): Keep imports and functions out of your namespace

    0.27-160000.2.2: noarch

    Source: perl-namespace-clean

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.