Upstream software project

perl-namespace-autoclean

Keep imports out of your namespace

About perl-namespace-autoclean

Keep imports out of your namespace

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-namespace-autoclean: 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-namespace-autoclean
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.

When you import a function into a Perl package, it will naturally also be available as a method. The 'namespace::autoclean' pragma will remove all imported symbols at the end of the current package's compile cycle. Functions called in the package itself will still be bound by their name, but they won't show up as methods on your class or instances. This module is very similar to namespace::clean, except it will clean all imported functions, no matter if you imported them before or after you 'use'd the pragma. It will also not touch anything that looks like a method. If you're writing an exporter and you want to clean up after yourself (and your peers), you can use the '-cleanee' switch to specify what package to clean: package My::MooseX::namespace::autoclean; use strict; use namespace::autoclean (); # no cleanup, just load sub import { namespace::autoclean->import( -cleanee => scalar(caller), ); }

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. Source: perl-namespace-autoclean

  2. Source: perl-namespace-autoclean

Alpine Linux 3.22

  1. Source: perl-namespace-autoclean

  2. Source: perl-namespace-autoclean

Alpine Linux 3.23

  1. Source: perl-namespace-autoclean

  2. Source: perl-namespace-autoclean

Debian 12 (Bookworm)

  1. Package libnamespace-autoclean-perl

    bookworm (Debian 12 (Bookworm)) (perl): module to remove imported symbols after compilation

    0.29-2: all

Debian 13 (Trixie)

Fedora 43

  1. Source: perl-namespace-autoclean

Fedora 44

  1. Source: perl-namespace-autoclean

openSUSE Leap 16.0

  1. Package perl-namespace-autoclean

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Keep imports out of your namespace

    0.310.0-160000.2.2: noarch

    Source: perl-namespace-autoclean

openSUSE Tumbleweed

  1. Package perl-namespace-autoclean

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Keep imports out of your namespace

    0.310.0-1.6: noarch

    Source: perl-namespace-autoclean

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.