%global _empty_manifest_terminate_build 0 Name: python-NamedAtomicLock Version: 1.1.3 Release: 1 Summary: Python module for an atomic named interprocess lock which is local to the machine. License: LGPLv3 URL: https://github.com/kata198/NamedAtomicLock Source0: https://mirrors.nju.edu.cn/pypi/web/packages/ae/61/3733fc4c371ece0fa820d8c3186e2d5c7b679bb32f37745508339e8c773e/NamedAtomicLock-1.1.3.tar.gz BuildArch: noarch %description Python module for an atomic named interprocess lock which is local to the machine. This means that this lock works across process boundries, so you can use it to lock objects that multiple processes would use. NamedAtomicLock works by taking advantage of the fact that POSIX defines mkdir to be an atomic operation. So a directory is used as the name. All UNIX systems are supported, overhead is light, and the lock is global to the system. The NamedAtomicLock module provides a class NamedAtomicLock which implements the "lock" interface, with familiar "acquire" and "release" methods. %package -n python3-NamedAtomicLock Summary: Python module for an atomic named interprocess lock which is local to the machine. Provides: python-NamedAtomicLock BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-NamedAtomicLock Python module for an atomic named interprocess lock which is local to the machine. This means that this lock works across process boundries, so you can use it to lock objects that multiple processes would use. NamedAtomicLock works by taking advantage of the fact that POSIX defines mkdir to be an atomic operation. So a directory is used as the name. All UNIX systems are supported, overhead is light, and the lock is global to the system. The NamedAtomicLock module provides a class NamedAtomicLock which implements the "lock" interface, with familiar "acquire" and "release" methods. %package help Summary: Development documents and examples for NamedAtomicLock Provides: python3-NamedAtomicLock-doc %description help Python module for an atomic named interprocess lock which is local to the machine. This means that this lock works across process boundries, so you can use it to lock objects that multiple processes would use. NamedAtomicLock works by taking advantage of the fact that POSIX defines mkdir to be an atomic operation. So a directory is used as the name. All UNIX systems are supported, overhead is light, and the lock is global to the system. The NamedAtomicLock module provides a class NamedAtomicLock which implements the "lock" interface, with familiar "acquire" and "release" methods. %prep %autosetup -n NamedAtomicLock-1.1.3 %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-NamedAtomicLock -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Mon May 15 2023 Python_Bot - 1.1.3-1 - Package Spec generated