Bug 904040 - Review Request: perl-Params-Check - Generic input parsing/checking mechanism
Summary: Review Request: perl-Params-Check - Generic input parsing/checking mechanism
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Petr Šabata
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 904058
TreeView+ depends on / blocked
 
Reported: 2013-01-25 10:25 UTC by Petr Pisar
Modified: 2013-02-18 08:41 UTC (History)
3 users (show)

Fixed In Version: perl-Params-Check-0.36-1.fc19
Clone Of:
Environment:
Last Closed: 2013-02-18 08:41:02 UTC
Type: ---
Embargoed:
psabata: fedora-review+


Attachments (Terms of Use)

Description Petr Pisar 2013-01-25 10:25:40 UTC
Spec URL: http://ppisar.fedorapeople.org/perl-Params-Check/perl-Params-Check.spec
SRPM URL: http://ppisar.fedorapeople.org/perl-Params-Check/perl-Params-Check-0.36-1.fc19.src.rpm
Description:
This is a generic input parsing/checking mechanism. It allows you to
validate input via a template. The only requirement is that the arguments
must be named.

Fedora Account System Username: ppisar

----
This is intended for rawhide only. It reincarnates already died perl-Params-Check to provide latest CPAN version and to replace perl's sub-package. This package will have been removed from perl core when releasing perl 5.20.

Comment 1 Petr Šabata 2013-02-13 15:28:03 UTC
No issues, approving...

Comment 2 Petr Pisar 2013-02-14 07:34:26 UTC
New Package SCM Request
=======================
Package Name: perl-Params-Check
Short Description: Generic input parsing/checking mechanism
Owners: ppisar jplesnik psabata
Branches: 
InitialCC: perl-sig

Comment 3 Gwyn Ciesla 2013-02-14 15:09:23 UTC
Unretired.

Comment 4 Petr Pisar 2013-02-15 09:12:55 UTC
Waiting on unblocking https://fedorahosted.org/rel-eng/ticket/5487.

Comment 5 Petr Pisar 2013-02-18 08:41:02 UTC
Thank you for the review and the repository.


Note You need to log in before you can comment on or make changes to this bug.