automatic import of python-dogpile-cache

3 files changed, 116 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..5531617 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/dogpile.cache-1.1.8.tar.gz
diff --git a/python-dogpile-cache.spec b/python-dogpile-cache.spec
new file mode 100644
index 0000000..1b46a89
--- /dev/null
+++ b/python-dogpile-cache.spec
@@ -0,0 +1,114 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-dogpile.cache
+Version:	1.1.8
+Release:	1
+Summary:	A caching front-end based on the Dogpile lock.
+License:	MIT
+URL:		https://github.com/sqlalchemy/dogpile.cache
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/e4/11/c5c200e774fb6cca03288c25cdb600fb8c41f2ace38a7ebfedfd3de3c3e1/dogpile.cache-1.1.8.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
+BuildRequires:	python3-pip
+%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.8
+
+%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
+* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 1.1.8-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..4d36c78
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+e27b4c16805bed19a77e68a67d1dc48d  dogpile.cache-1.1.8.tar.gz