rpms/perl-Perl-Critic/devel perl-Perl-Critic.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2

Jose Pedro Oliveira (jpo) fedora-extras-commits at redhat.com
Sat Sep 23 17:07:15 UTC 2006


Author: jpo

Update of /cvs/extras/rpms/perl-Perl-Critic/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15793/devel

Modified Files:
	.cvsignore sources 
Added Files:
	perl-Perl-Critic.spec 
Log Message:
auto-import perl-Perl-Critic-0.2-1 on branch devel from perl-Perl-Critic-0.2-1.src.rpm


--- NEW FILE perl-Perl-Critic.spec ---
Name:           perl-Perl-Critic
Version:        0.2
Release:        1%{?dist}
Summary:        Critique Perl source code for best-practices

Group:          Development/Libraries
License:        GPL or Artistic
URL:            http://search.cpan.org/dist/Perl-Critic/
Source0:        http://www.cpan.org/authors/id/T/TH/THALJEF/perlcritic/Perl-Critic-%{version}.tar.gz
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildArch:      noarch
BuildRequires:  perl(Module::Build)
BuildRequires:  perl(Config::Tiny) >= 2
BuildRequires:  perl(IO::String)
BuildRequires:  perl(List::MoreUtils)
BuildRequires:  perl(Module::Pluggable)
BuildRequires:  perl(PPI) >= 1.117
BuildRequires:  perl(String::Format) >= 1.13
BuildRequires:  perl(Perl::Tidy)
BuildRequires:  perl(Test::Pod)
BuildRequires:  perl(Test::Pod::Coverage)
Requires:       perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version))
Requires:       perl(Module::Pluggable)
Requires(hint): perl(Perl::Tidy)

%description
Perl::Critic is an extensible framework for creating and applying coding
standards to Perl source code. Essentially, it is a static source code
analysis engine. Perl::Critic is distributed with a number of
Perl::Critic::Policy modules that attempt to enforce various coding
guidelines. Most Policy modules are based on Damian Conway's book Perl
Best Practices. However, Perl::Critic is not limited to PBP and will
even support Policies that contradict Conway. You can enable, disable,
and customize those Polices through the Perl::Critic interface. You can
also create new Policy modules that suit your own tastes.


%prep
%setup -q -n Perl-Critic-%{version}


%build
%{__perl} Build.PL installdirs=vendor
./Build


%install
rm -rf $RPM_BUILD_ROOT
./Build install destdir=$RPM_BUILD_ROOT create_packlist=0
chmod -R u+w $RPM_BUILD_ROOT/*


%check
./Build test


%clean
rm -rf $RPM_BUILD_ROOT


%files
%defattr(-,root,root,-)
%doc Changes LICENSE README TODO.pod
%{_bindir}/*
%{perl_vendorlib}/Perl/
%{_mandir}/man1/*.1*
%{_mandir}/man3/*.3pm*


%changelog
* Sat Sep 16 2006 Jose Pedro Oliveira <jpo at di.uminho.pt> - 0.2-1
- First build.


Index: .cvsignore
===================================================================
RCS file: /cvs/extras/rpms/perl-Perl-Critic/devel/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- .cvsignore	23 Sep 2006 17:06:30 -0000	1.1
+++ .cvsignore	23 Sep 2006 17:07:14 -0000	1.2
@@ -0,0 +1 @@
+Perl-Critic-0.2.tar.gz


Index: sources
===================================================================
RCS file: /cvs/extras/rpms/perl-Perl-Critic/devel/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sources	23 Sep 2006 17:06:30 -0000	1.1
+++ sources	23 Sep 2006 17:07:14 -0000	1.2
@@ -0,0 +1 @@
+a31ab7c92cdb0501c1a3e298495f61c5  Perl-Critic-0.2.tar.gz




More information about the scm-commits mailing list