perl-Pod-Coverage/perl-Pod-Coverage.spec
cvsextras f0c119c45e auto-import perl-Pod-Coverage-0.14-0.fdr.1.1 from
perl-Pod-Coverage-0.14-0.fdr.1.1.src.rpm
2004-11-08 05:07:02 +00:00

66 lines
1.8 KiB
RPMSpec

%{!?perl_vendorarch: %define perl_vendorarch %(eval "`perl -V:installvendorarch`"; echo $installvendorarch)}
Name: perl-Pod-Coverage
Version: 0.14
Release: 0.fdr.1.1
Epoch: 0
Summary: Checks if the documentation of a module is comprehensive
Group: Development/Libraries
License: GPL or Artistic
URL: http://search.cpan.org/dist/Pod-Coverage/
Source0: http://www.cpan.org/authors/id/R/RC/RCLAMP/Pod-Coverage-0.14.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildRequires: perl(Module::Build)
BuildRequires: perl(Devel::Symdump), perl(Test::More), perl(Test::Pod)
Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version))
%description
Developers hate writing documentation. They'd hate it even more if their
computer tattled on them, but maybe they'll be even more thankful in the
long run. Even if not, perlmodstyle tells you to, so you must obey.
This module provides a mechanism for determining if the pod for a given
module is comprehensive.
%prep
%setup -q -n Pod-Coverage-%{version}
%build
CFLAGS="$RPM_OPT_FLAGS" %{__perl} Build.PL installdirs=vendor
./Build
%install
rm -rf $RPM_BUILD_ROOT
./Build install destdir=$RPM_BUILD_ROOT
find $RPM_BUILD_ROOT -type f -a \( -name .packlist \
-o \( -name '*.bs' -a -empty \) \) -exec rm -f {} ';'
find $RPM_BUILD_ROOT -type d -depth -exec rmdir {} 2>/dev/null ';'
chmod -R u+w $RPM_BUILD_ROOT/*
%check || :
./Build test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes README examples/
%{_bindir}/*
%{perl_vendorarch}/Pod/
%{perl_vendorarch}/auto/Pod/
%{_mandir}/man3/*.3*
%changelog
* Thu May 20 2004 Jose Pedro Oliveira <jpo at di.uminho.pt> - 0:0.14-0.fdr.1
- First build.