114 lines
4.9 KiB
RPMSpec
114 lines
4.9 KiB
RPMSpec
%global _empty_manifest_terminate_build 0
|
|
Name: python-dogpile-cache
|
|
Version: 1.1.0
|
|
Release: 1
|
|
Summary: A caching front-end based on the Dogpile lock.
|
|
License: MIT
|
|
URL: https://github.com/sqlalchemy/dogpile.cache
|
|
Source0: https://files.pythonhosted.org/packages/3d/2c/88f428ceb69604ea64dc5b84a79784dc410c40cbc8f023210e93028573db/dogpile.cache-1.1.0.tar.gz
|
|
BuildArch: noarch
|
|
|
|
|
|
%description
|
|
Dogpile consists of two subsystems, one building on top of the other.
|
|
``dogpile`` provides the concept of a "dogpile lock", a control structure
|
|
which allows a single thread of execution to be selected as the "creator" of
|
|
some resource, while allowing other threads of execution to refer to the previous
|
|
version of this resource as the creation proceeds; if there is no previous
|
|
version, then those threads block until the object is available.
|
|
``dogpile.cache`` is a caching API which provides a generic interface to
|
|
caching backends of any variety, and additionally provides API hooks which
|
|
integrate these cache backends with the locking mechanism of ``dogpile``.
|
|
Overall, dogpile.cache is intended as a replacement to the `Beaker
|
|
<https://pypi.org/project/Beaker/>`_ caching system, the internals of which are
|
|
written by the same author. All the ideas of Beaker which "work" are re-
|
|
implemented in dogpile.cache in a more efficient and succinct manner, and all
|
|
the cruft (Beaker's internals were first written in 2005) relegated to the
|
|
trash heap.
|
|
|
|
%package -n python3-dogpile-cache
|
|
Summary: A caching front-end based on the Dogpile lock.
|
|
Provides: python-dogpile-cache
|
|
BuildRequires: python3-devel
|
|
BuildRequires: python3-setuptools
|
|
%description -n python3-dogpile-cache
|
|
Dogpile consists of two subsystems, one building on top of the other.
|
|
``dogpile`` provides the concept of a "dogpile lock", a control structure
|
|
which allows a single thread of execution to be selected as the "creator" of
|
|
some resource, while allowing other threads of execution to refer to the previous
|
|
version of this resource as the creation proceeds; if there is no previous
|
|
version, then those threads block until the object is available.
|
|
``dogpile.cache`` is a caching API which provides a generic interface to
|
|
caching backends of any variety, and additionally provides API hooks which
|
|
integrate these cache backends with the locking mechanism of ``dogpile``.
|
|
Overall, dogpile.cache is intended as a replacement to the `Beaker
|
|
<https://pypi.org/project/Beaker/>`_ caching system, the internals of which are
|
|
written by the same author. All the ideas of Beaker which "work" are re-
|
|
implemented in dogpile.cache in a more efficient and succinct manner, and all
|
|
the cruft (Beaker's internals were first written in 2005) relegated to the
|
|
trash heap.
|
|
|
|
%package help
|
|
Summary: Development documents and examples for dogpile.cache
|
|
Provides: python3-dogpile-cache-doc
|
|
%description help
|
|
Dogpile consists of two subsystems, one building on top of the other.
|
|
``dogpile`` provides the concept of a "dogpile lock", a control structure
|
|
which allows a single thread of execution to be selected as the "creator" of
|
|
some resource, while allowing other threads of execution to refer to the previous
|
|
version of this resource as the creation proceeds; if there is no previous
|
|
version, then those threads block until the object is available.
|
|
``dogpile.cache`` is a caching API which provides a generic interface to
|
|
caching backends of any variety, and additionally provides API hooks which
|
|
integrate these cache backends with the locking mechanism of ``dogpile``.
|
|
Overall, dogpile.cache is intended as a replacement to the `Beaker
|
|
<https://pypi.org/project/Beaker/>`_ caching system, the internals of which are
|
|
written by the same author. All the ideas of Beaker which "work" are re-
|
|
implemented in dogpile.cache in a more efficient and succinct manner, and all
|
|
the cruft (Beaker's internals were first written in 2005) relegated to the
|
|
trash heap.
|
|
|
|
%prep
|
|
%autosetup -n dogpile.cache-1.1.0
|
|
|
|
%build
|
|
%py3_build
|
|
|
|
%install
|
|
%py3_install
|
|
install -d -m755 %{buildroot}/%{_pkgdocdir}
|
|
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
|
|
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
|
|
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
|
|
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
|
|
pushd %{buildroot}
|
|
if [ -d usr/lib ]; then
|
|
find usr/lib -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/bin ]; then
|
|
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
|
|
fi
|
|
if [ -d usr/sbin ]; then
|
|
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
|
|
fi
|
|
touch doclist.lst
|
|
if [ -d usr/share/man ]; then
|
|
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
|
|
fi
|
|
popd
|
|
mv %{buildroot}/filelist.lst .
|
|
mv %{buildroot}/doclist.lst .
|
|
|
|
%files -n python3-dogpile-cache -f filelist.lst
|
|
%dir %{python3_sitelib}/*
|
|
|
|
%files help -f doclist.lst
|
|
%{_docdir}/*
|
|
|
|
%changelog
|
|
* Sat Nov 21 2020 Python_Bot <Python_Bot@openeuler.org>
|
|
- Package Spec generated
|