The Exporter module implements an import method which allows a module to
export functions and variables to its users' name spaces. Many modules use
Exporter rather than implementing their own import method because Exporter
provides a highly flexible interface, with an implementation optimized for
the common case.
No published records match this suite and architecture filter.
Package file paths (8)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
/usr/share/doc/perl-Exporter
/usr/share/doc/perl-Exporter/Changes
/usr/share/doc/perl-Exporter/README
/usr/share/man/man3/Exporter.3pm.gz
/usr/share/man/man3/Exporter::Heavy.3pm.gz
/usr/share/perl5/vendor_perl/Exporter
/usr/share/perl5/vendor_perl/Exporter/Heavy.pm
/usr/share/perl5/vendor_perl/Exporter.pm
Use this package
OpenFactory can boot this operating system in a browser VM, or start a build that includes the native package name from this record.
Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.
No published records match this suite and architecture filter.
Checksums and observation dates
For an APT source, signature verification authenticates the repository metadata chain and the Packages index containing this source-reported artifact digest. It does not certify package safety.
Catalog record completeness
The completeness score measures metadata coverage, not software quality, security, compatibility, or suitability.
