%define pkg_name        Filter-Macro
%define pkg_version     0.11
%define rpm_pkg_version 0.11
%define rpm_pkg_release 2.n0i.2

Summary:       Make macro modules that are expanded inline
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:       http://www.cpan.org/authors/id/A/AU/AUTRIJUS/%{pkg_name}-%{pkg_version}.tar.gz

BuildArch:     noarch
BuildRoot:     %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildRequires: reb00t-rpmdevtools
BuildRequires: perl(ExtUtils::MakeMaker)
%{!?_without_test:BuildRequires: perl(Filter::Simple::Compile)}


%description
If many of your programs begin with the same lines, it may make sense to
abstract them away into a module, and "use" that module instead. Sadly, it
does not work that way, because by default, all lexical pragmas, source
filters and subroutine imports invoked in MyHandyModules.pm takes effect in
that module, *not* the calling programs.
With this module, a program or module that says "use Filter::Macro" will
expand lines below "use Filter::Macro" into their own code, instead of the
default semantic of evaluating them in the "MyHandyModules" package.
Line numbers in error and warning messages are unaffected by this module;
they still point to the correct file name and line numbers.


%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 README


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

* Sat May 13 2006 Marius Feraru <altblue@n0i.net> 0.11-1.n0i.1
- spec file (re)created using N0i::CPAN::RPMizer v1.12.1
- rebuild on perl 5.8.8