1 |
%define upstream_name Test-Kwalitee |
2 |
%define upstream_version 1.01 |
3 |
|
4 |
Name: perl-%{upstream_name} |
5 |
Version: %perl_convert_version %{upstream_version} |
6 |
Release: %mkrel 1 |
7 |
|
8 |
Summary: Test the Kwalitee of a distribution before you release it |
9 |
License: GPL+ or Artistic |
10 |
Group: Development/Perl |
11 |
Url: http://search.cpan.org/dist/%{upstream_name} |
12 |
Source0: http://www.cpan.org/modules/by-module/Test/%{upstream_name}-%{upstream_version}.tar.bz2 |
13 |
|
14 |
BuildRequires: perl-version |
15 |
BuildRequires: perl(Module::CPANTS::Analyse) |
16 |
BuildRequires: perl(Module::Build) |
17 |
BuildArch: noarch |
18 |
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release} |
19 |
|
20 |
%description |
21 |
Kwalitee is an automatically-measurable gauge of how good your software is. |
22 |
That's very different from quality, which a computer really can't measure in a |
23 |
general sense. (If you can, you've solved a hard problem in computer science.) |
24 |
|
25 |
In the world of the CPAN, the CPANTS project (CPAN Testing Service; also a |
26 |
funny acronym on its own) measures Kwalitee with several metrics. If you plan |
27 |
to release a distribution to the CPAN -- or even within your own organization |
28 |
-- testing its Kwalitee before creating a release can help you improve your |
29 |
quality as well. |
30 |
|
31 |
Test::Kwalitee and a short test file will do this for you automatically. |
32 |
|
33 |
%prep |
34 |
%setup -q -n %{upstream_name}-%{upstream_version} |
35 |
|
36 |
%build |
37 |
%{__perl} Build.PL installdirs=vendor |
38 |
./Build |
39 |
|
40 |
%check |
41 |
./Build test |
42 |
|
43 |
%install |
44 |
rm -rf %{buildroot} |
45 |
./Build install destdir=%{buildroot} |
46 |
|
47 |
%clean |
48 |
rm -rf %{buildroot} |
49 |
|
50 |
%files |
51 |
%defattr(-,root,root) |
52 |
%doc ChangeLog README |
53 |
%{perl_vendorlib}/Test |
54 |
%{_mandir}/*/* |
55 |
|
56 |
|