Split Test::Perl::Critic::Policy off into its own package

perl-Perl-Critic.spec

@@ -84,6 +84,19 @@ and customize those Polices through the Perl::Critic interface. You can
 also create new Policy modules that suit your own tastes.
 
 
+%package -n perl-Test-Perl-Critic-Policy
+Summary:        A framework for testing your custom Policies
+Group:          Development/Libraries
+License:        GPL+ or Artistic
+
+
+%description -n perl-Test-Perl-Critic-Policy
+This module provides a framework for function-testing your custom
+Perl::Critic::Policy modules. Policy testing usually involves feeding it a
+string of Perl code and checking its behavior. In the old days, those strings
+of Perl code were mixed directly in the test script. That sucked.
+
+
 %prep
 %setup -q -n Perl-Critic-%{version}
 find . -type f -exec chmod -c -x {} +
@@ -109,11 +122,16 @@ find . -type f -exec chmod -c -x {} +
 %files
 %defattr(-,root,root,-)
 %doc Changes LICENSE README TODO.pod examples/ extras/ tools/
-%{_bindir}/*
+%{_bindir}/perlcritic
 %{perl_vendorlib}/Perl/
-%{perl_vendorlib}/Test/*
-%{_mandir}/man1/*.1*
-%{_mandir}/man3/*.3pm*
+%{_mandir}/man1/perlcritic.1*
+%{_mandir}/man3/Perl::Critic*.3pm*
+
+
+%files -n perl-Test-Perl-Critic-Policy
+%defattr(-,root,root,-)
+%{perl_vendorlib}/Test/
+%{_mandir}/man3/Test::Perl::Critic::Policy.3pm*
 
 
 %changelog
@@ -145,6 +163,7 @@ find . -type f -exec chmod -c -x {} +
 - bump PPI version requirement to 1.215
 - BR/R: perl(Pod::Parser)
 - drop redundant (for modern rpm) BuildRoot tag and buildroot cleaning
+- split Test::Perl::Critic::Policy off into its own package
 
 * Mon Mar  7 2011 Marcela Mašláňová <mmaslano@redhat.com> - 1.113-1
 - update to 1.113