Name:           perl-Call-Context
Version:        0.05
Release:        %autorelease
Summary:        Sanity-check calling context

License:        MIT

URL:            https://metacpan.org/dist/Call-Context
Source0:        https://cpan.metacpan.org/authors/id/F/FE/FELIPE/Call-Context-%{version}.tar.gz

BuildArch:      noarch

BuildRequires:  make
BuildRequires:  perl-generators
BuildRequires:  perl-interpreter
BuildRequires:  perl(ExtUtils::MakeMaker)
BuildRequires:  perl(Test::More) >= 0.44

%{?perl_default_filter}


%description
If your function only expects to return a list, then a call in some
other context is, by definition, an error. The problem is that,
depending on how the function is written, it may actually do something
expected in testing, but then in production act differently.

%prep
%autosetup -n Call-Context-%{version}


%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
%make_build


%install
make pure_install DESTDIR=$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


%files
%license LICENSE
%doc Changes
%doc README.md
%{perl_vendorlib}/*
%exclude %dir %{perl_vendorarch}/auto/
%{_mandir}/man3/*.3*


%changelog
%autochangelog