From c5f5233fd60c87cbbf4c9db5a0cec7b145321182 Mon Sep 17 00:00:00 2001 From: Daniel Berteaud Date: Fri, 11 Feb 2022 16:51:16 +0100 Subject: [PATCH] Import Sub::Exporter::Progressive --- .gitattributes | 1 + Sub-Exporter-Progressive-0.001013.tar.gz | 3 ++ perl-Sub-Exporter-Progressive.spec | 54 ++++++++++++++++++++++++ 3 files changed, 58 insertions(+) create mode 100644 .gitattributes create mode 100644 Sub-Exporter-Progressive-0.001013.tar.gz create mode 100644 perl-Sub-Exporter-Progressive.spec diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 0000000..f087b42 --- /dev/null +++ b/.gitattributes @@ -0,0 +1 @@ +*.tar.gz filter=lfs diff=lfs merge=lfs -text diff --git a/Sub-Exporter-Progressive-0.001013.tar.gz b/Sub-Exporter-Progressive-0.001013.tar.gz new file mode 100644 index 0000000..b81ed50 --- /dev/null +++ b/Sub-Exporter-Progressive-0.001013.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d535b7954d64da1ac1305b1fadf98202769e3599376854b2ced90c382beac056 +size 13468 diff --git a/perl-Sub-Exporter-Progressive.spec b/perl-Sub-Exporter-Progressive.spec new file mode 100644 index 0000000..9f4e32d --- /dev/null +++ b/perl-Sub-Exporter-Progressive.spec @@ -0,0 +1,54 @@ +Name: perl-Sub-Exporter-Progressive +Version: 0.001013 +Release: 1%{?dist} +Summary: Only use Sub::Exporter if you need it +License: GPL+ or Artistic +Group: Development/Libraries +URL: http://search.cpan.org/dist/Sub-Exporter-Progressive/ +Source0: http://www.cpan.org/authors/id/F/FR/FREW/Sub-Exporter-Progressive-%{version}.tar.gz +BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) +BuildArch: noarch +BuildRequires: perl(ExtUtils::MakeMaker) +BuildRequires: perl(Test::More) >= 0.88 +Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version)) + +%description +Sub::Exporter is an incredibly powerful module, but with that power comes +great responsibility, er- as well as some runtime penalties. This module is +a Sub::Exporter wrapper that will let your users just use Exporter if all +they are doing is picking exports, but use Sub::Exporter if your users try +to use Sub::Exporter's more advanced features, like renaming exports, if +they try to use them. + +%prep +%setup -q -n Sub-Exporter-Progressive-%{version} + +%build +%{__perl} Makefile.PL INSTALLDIRS=vendor +make %{?_smp_mflags} + +%install +rm -rf $RPM_BUILD_ROOT + +make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT + +find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \; +find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \; + +%{_fixperms} $RPM_BUILD_ROOT/* + +%check +make test + +%clean +rm -rf $RPM_BUILD_ROOT + +%files +%defattr(-,root,root,-) +%doc Changes cpanfile dist.ini LICENSE META.json README +%{perl_vendorlib}/* +%{_mandir}/man3/* + +%changelog +* Fri Feb 11 2022 Daniel Berteaud 0.001013-1 +- Specfile autogenerated by cpanspec 1.78.