Packaging CPAN modules for Fedora, the Oslo QA Hackathon, CPAN::Porters

[Chris Weyl]

On 11 Mar 2008 14:18:07 -0500, Jason L Tibbitts III <tibbs at math.uh.edu> wrote:

> >>>>> "DC" == Dave Cross <dave at dave.org.uk> writes:
>
> DC> I've always had a sneaking suspicion that what I've got are good
> DC> enough for me, but not for Fedora's repositories.
>
> Well, modern cpanspec generates pretty good specs.  Generally what you
> need to do is verify the license (which unfortunately seems to be the
> most time-consuming bit these days), change the License: tag
> appropriately, and add build dependencies (BuildRequires:) sufficient
> to get the module to build in mock and be able to run as much of its
> test suite properly.  A quick glance over the Summary: and
> %description helps as well.
>
> If the license is unambiguous, this takes a couple of minutes plus
> whatever time it takes mock to run.  Submitting the review takes a
> couple of minutes more.  Generally Perl packages are reviewed quickly
> because the reviewer usually just needs to verify that you've done the
> stuff in the previous paragraph.

The perl guidelines at
http://fedoraproject.org/wiki/PackagingDrafts/Perl often help point
out the perl-specific bits, as well.

IMHO, of course :)

                                                 -Chris
-- 
Chris Weyl
Ex astris, scientia