%define pkg_name        PluceneSimple
%define pkg_version     1.04
%define rpm_pkg_version 1.04
%define rpm_pkg_release 2.n0i.2

Summary:       An interface to Plucene
Name:          perl-%{pkg_name}
Version:       %{rpm_pkg_version}
Release:       %{rpm_pkg_release}%{?cpan_version}%{?dist}

Group:         Development/Libraries
License:       Artistic
URL:           http://search.cpan.org/dist/%{pkg_name}/
Source0:       /%{pkg_name}-%{pkg_version}.tar.gz

BuildArch:     noarch
BuildRoot:     %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildRequires: reb00t-rpmdevtools
BuildRequires: perl(Module::Build)

%if %{!?_without_test:1}0
BuildRequires: perl(File::Find::Rule) >= 0.10
BuildRequires: perl(File::Path) >= 1.05
BuildRequires: perl(File::Slurp) >= 2002.1031
BuildRequires: perl(File::Spec::Functions) >= 1.2
BuildRequires: perl(Plucene) >= 1.09
BuildRequires: perl(Test::Class) >= 0.03
BuildRequires: perl(Test::Harness) >= 2.30
BuildRequires: perl(Time::Piece) >= 1.08
BuildRequires: perl(Time::Piece::Range) >= 1.0
%endif


%description
This provides a simple interface to Plucene. Plucene is large and
multi-featured, and it expected that users will subclass it, and tie all
the pieces together to suit their own needs. Plucene::Simple is, therefore,
just one way to use Plucene. It's not expected that it will do exactly what
*you* want, but you can always use it as an example of how to build your
own interface.


%prep
%setup -q -n %{pkg_name}-%{pkg_version}


%build
%{perl_build}
%{!?_without_test:%{__make} test}


%install
%{__rm} -rf $RPM_BUILD_ROOT
%{perl_install}


%clean
%{__rm} -rf $RPM_BUILD_ROOT


%files
%defattr(-,root,root,-)
%{perl_files}
%doc Changes


%changelog
* Tue May 22 2007 Marius Feraru <altblue@n0i.net> - 1.04-2.n0i.2
- spec file (re)created using N0i::CPAN::RPMizer v1.14.7
- rebuild on perl 5.8.8

* Tue Aug 09 2005 Marius Feraru <altblue@n0i.net> 1.04-1.n0i.1
- spec file (re)created using N0i::CPAN::RPMizer/1.01
- rebuild on perl 5.8.7