To assist packagers in bringing Perl-related packages to Fedora Extras and assisting in their continued maintenance by providing timely reviews, acting as secondary package owners and assisting with related security issues.

+

To assist packagers in bringing Perl-related packages to Fedora and assisting in their continued maintenance by providing timely reviews, acting as secondary package owners and assisting with related security issues.

= Perl Components in Fedora =

= Perl Components in Fedora =

Line 9:

Line 9:

== Core Perl ==

== Core Perl ==

−

Core perl in Fedora-16 is currently 5.14.1.

+

[http://search.cpan.org/~dom/perl/|Core perl] in Fedora is defined by perl-core package. Some core modules are replaced with packages dual-living on CPAN. [https://koji.fedoraproject.org/koji/packageinfo?packageID=84 See koji build listing for current perl version.]

Fedora Perl SIG Mission

To assist packagers in bringing Perl-related packages to Fedora and assisting in their continued maintenance by providing timely reviews, acting as secondary package owners and assisting with related security issues.

Fedora perl infrastructure

Perl to CPAN Mapping

With most perl modules being in CPAN, preliminary "mapping" table has been created. This table is regenerated on a daily basis, and will be included in the upcoming Perl SIG Infrastructure hosted project .

at least try to handle use statements a litte better (eg: use base Module; use autouse Module; ...)

Use PPI?

Try to have RPM patched in order to create the debuginfo files after the %check section script is executed and not before (right now the files are created after the %install check script is executed). This breaks the signature tests (there are also other problems related to the signature tests in the building environment: network access to import pgg keys, where should they be stored, ...). More information available here and in bug #167252 .

Miscellaneous

Clarified packaging guidelines - Some of the packaging guidelines (see Packaging/Perl) have conflicted with some common practises.

For example, BuildRequires: perl was common but forbidden; that has now been changed. One current issue is the prohibition against including header files in the main package; some perl modules include these deep in the module directory hierarchy, and moving them to a separate -devel package is pointless.