File _service:obs_scm:perl-DBD-Mock.spec of Package perl-DBD-Mock

%global _empty_manifest_terminate_build 0
Name:           perl-DBD-Mock
Version:        1.59
Release:        1
Summary:        Mock database driver for testing
License:        GPL-1.0-only or Artistic-1.0-perl
Group:          Development/Libraries
URL:            http://search.cpan.org/dist/DBD-Mock/
Source0:        http://www.cpan.org/authors/id/J/JL/JLCOOPER/DBD-Mock-%{version}.tar.gz
BuildArch:      noarch
BuildRequires:  perl >= 0:5.008001
BuildRequires:  perl-generators
BuildRequires:  perl(DBI) >= 1.3
BuildRequires:  perl(List::Util) >= 1.27
BuildRequires:  perl(Module::Build)
BuildRequires:  perl(Test::Exception) >= 0.31
BuildRequires:  perl(Test::More) >= 0.47
BuildRequires:  perl(Module::Build::Tiny)
Requires:       perl(DBI) >= 1.3
Requires:       perl(List::Util) >= 1.27
%description
Testing with databases can be tricky. If you are developing a system
married to a single database then you can make some assumptions about your
environment and ask the user to provide relevant connection information.
But if you need to test a framework that uses DBI, particularly a framework
that uses different types of persistence schemes, then it may be more
useful to simply verify what the framework is trying to do -- ensure the
right SQL is generated and that the correct parameters are bound. DBD::Mock
makes it easy to just modify your configuration (presumably held outside
your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql)
in your framework.
%package help
Summary : Mock database driver for testing
Provides: perl-DBD-Mock-doc
%description help
Testing with databases can be tricky. If you are developing a system
married to a single database then you can make some assumptions about your
environment and ask the user to provide relevant connection information.
But if you need to test a framework that uses DBI, particularly a framework
that uses different types of persistence schemes, then it may be more
useful to simply verify what the framework is trying to do -- ensure the
right SQL is generated and that the correct parameters are bound. DBD::Mock
makes it easy to just modify your configuration (presumably held outside
your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql)
in your framework.
%prep
%setup -q -n DBD-Mock-%{version}
%build
export PERL_MM_OPT=""
%{__perl} Build.PL --installdirs=vendor
./Build

%install
export PERL_MM_OPT=""
rm -rf $RPM_BUILD_ROOT

./Build install --destdir=$RPM_BUILD_ROOT --create_packlist=0
find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \;

%{_fixperms} $RPM_BUILD_ROOT/*

pushd %{buildroot}
touch filelist.lst
if [ -d usr/bin ];then
    find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ];then
    find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ];then
    find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib ];then
    find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
popd
mv %{buildroot}/filelist.lst .
%check || :
./Build test

%clean
rm -rf $RPM_BUILD_ROOT

%files -f filelist.lst
%defattr(-,root,root,-)
%doc Changes CONTRIBUTING.md cpanfile LICENSE META.json minil.toml README.md
%{perl_vendorlib}/*
%files help
%{_mandir}/*

%changelog
* Sun May 23 2021 Perl_Bot <Perl_Bot@openeuler.org> 1.59-1
- Specfile autogenerated by Perl_Bot