summaryrefslogtreecommitdiff
path: root/python-kazurator.spec
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-04-10 17:01:35 +0000
committerCoprDistGit <infra@openeuler.org>2023-04-10 17:01:35 +0000
commit82161415def7d94cf62ece52c1616833f84f98af (patch)
treea0687984e84dc4438fb3788728f27e77c4b9e5c1 /python-kazurator.spec
parent51f72b9db0a3e0c530e9b426d473fe10c13b6c70 (diff)
automatic import of python-kazurator
Diffstat (limited to 'python-kazurator.spec')
-rw-r--r--python-kazurator.spec114
1 files changed, 114 insertions, 0 deletions
diff --git a/python-kazurator.spec b/python-kazurator.spec
new file mode 100644
index 0000000..e4b9af1
--- /dev/null
+++ b/python-kazurator.spec
@@ -0,0 +1,114 @@
+%global _empty_manifest_terminate_build 0
+Name: python-kazurator
+Version: 0.2.0
+Release: 1
+Summary: Inter process lock recipes that play nice with curator
+License: MIT
+URL: https://github.com/pseudomuto/kazurator
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/1e/ea/ff05e74d950cf168606cef092e63d8777895ed1627a4b445258c65771a39/kazurator-0.2.0.tar.gz
+BuildArch: noarch
+
+Requires: python3-kazoo
+Requires: python3-kazoo
+Requires: python3-flake8
+Requires: python3-nose
+Requires: python3-pep8
+Requires: python3-tox
+
+%description
+|PyPI| |Build Status|
+A python port of the `Shared Reentrant Read Write Lock`_ recipe from `curator`_. This package dependends on `kazoo`_ for
+handling the zookeeper bits.
+At this point, you're probably wondering why I didn't just use the existing locks recipe from `kazoo`_. The original
+goal was to make `curator`_ and `kazoo`_ respect each other's locks such that:
+1. Either could acquire a read lock, so long as neither held a write
+ lock
+2. Either could acquire a write lock, and block either from acquiring
+ either read/write locks
+I first attempted to patch the locks recipe in `kazoo`_, but the internals are a bit different. (**READ**: *I wasn't
+able to make it work right*).
+The reason this is necessary (at least for me), is that some code was running Scala and using `curator`_, and other code
+was running Python using `kazoo`_.
+
+%package -n python3-kazurator
+Summary: Inter process lock recipes that play nice with curator
+Provides: python-kazurator
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-kazurator
+|PyPI| |Build Status|
+A python port of the `Shared Reentrant Read Write Lock`_ recipe from `curator`_. This package dependends on `kazoo`_ for
+handling the zookeeper bits.
+At this point, you're probably wondering why I didn't just use the existing locks recipe from `kazoo`_. The original
+goal was to make `curator`_ and `kazoo`_ respect each other's locks such that:
+1. Either could acquire a read lock, so long as neither held a write
+ lock
+2. Either could acquire a write lock, and block either from acquiring
+ either read/write locks
+I first attempted to patch the locks recipe in `kazoo`_, but the internals are a bit different. (**READ**: *I wasn't
+able to make it work right*).
+The reason this is necessary (at least for me), is that some code was running Scala and using `curator`_, and other code
+was running Python using `kazoo`_.
+
+%package help
+Summary: Development documents and examples for kazurator
+Provides: python3-kazurator-doc
+%description help
+|PyPI| |Build Status|
+A python port of the `Shared Reentrant Read Write Lock`_ recipe from `curator`_. This package dependends on `kazoo`_ for
+handling the zookeeper bits.
+At this point, you're probably wondering why I didn't just use the existing locks recipe from `kazoo`_. The original
+goal was to make `curator`_ and `kazoo`_ respect each other's locks such that:
+1. Either could acquire a read lock, so long as neither held a write
+ lock
+2. Either could acquire a write lock, and block either from acquiring
+ either read/write locks
+I first attempted to patch the locks recipe in `kazoo`_, but the internals are a bit different. (**READ**: *I wasn't
+able to make it work right*).
+The reason this is necessary (at least for me), is that some code was running Scala and using `curator`_, and other code
+was running Python using `kazoo`_.
+
+%prep
+%autosetup -n kazurator-0.2.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-kazurator -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.2.0-1
+- Package Spec generated