- new

Changed files:
    perl-Sub-Override.spec -> 1.1

diff --git a/perl-Sub-Override.spec b/perl-Sub-Override.spec
new file mode 100644 (file)
index 0000000..1676f46
--- /dev/null
+++ b/perl-Sub-Override.spec
@@ -0,0 +1,62 @@
+#
+# Conditional build:
+%bcond_without tests           # do not perform "make test"
+#
+%include       /usr/lib/rpm/macros.perl
+%define        pdir    Sub
+%define        pnam    Override
+Summary:       Sub::Override - Perl extension for easily overriding subroutines
+#Summary(pl):  
+Name:          perl-Sub-Override
+Version:       0.05
+Release:       1
+# same as perl
+License:       GPL v1+ or Artistic
+Group:         Development/Languages/Perl
+Source0:       http://www.cpan.org/modules/by-module/%{pdir}/%{pdir}-%{pnam}-%{version}.tar.gz
+# Source0-md5: 3abc240ed157535aaf90de3e59fd6cf2
+BuildRequires: perl-devel >= 1:5.8.0
+BuildRequires: rpm-perlprov >= 4.1-13
+%if %{with tests}
+BuildRequires: perl-Test-Exception >= 0.15
+BuildRequires: perl-Test-Simple >= 0.47
+%endif
+BuildArch:     noarch
+BuildRoot:     %{tmpdir}/%{name}-%{version}-root-%(id -u -n)
+
+%description
+Sometimes subroutines need to be overridden.  In fact, your author does
+this constantly for tests.  Particularly when testing, using a Mock
+Object can be overkill when all you want to do is override one tiny,
+little function.
+
+Sub::Override allows the programmer to simply name the sub to replace
+and to supply a sub to replace it with.
+
+# %description -l pl
+# TODO
+
+%prep
+%setup -q -n %{pdir}-%{pnam}-%{version}
+
+%build
+%{__perl} Makefile.PL \
+       INSTALLDIRS=vendor
+%{__make}
+
+%{?with_tests:%{__make} test}
+
+%install
+rm -rf $RPM_BUILD_ROOT
+
+%{__make} install \
+       DESTDIR=$RPM_BUILD_ROOT
+
+%clean
+rm -rf $RPM_BUILD_ROOT
+
+%files
+%defattr(644,root,root,755)
+%doc Changes README
+%{perl_vendorlib}/Sub/*.pm
+%{_mandir}/man3/*