diff options
Diffstat (limited to 'python-amqpconnector.spec')
| -rw-r--r-- | python-amqpconnector.spec | 132 |
1 files changed, 132 insertions, 0 deletions
diff --git a/python-amqpconnector.spec b/python-amqpconnector.spec new file mode 100644 index 0000000..22046de --- /dev/null +++ b/python-amqpconnector.spec @@ -0,0 +1,132 @@ +%global _empty_manifest_terminate_build 0 +Name: python-AmqpConnector +Version: 0.0.41 +Release: 1 +Summary: Simple library for building a distributed task system over AMQP. +License: UNKNOWN +URL: http://pypi.python.org/pypi/AmqpConnector/ +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/61/27/4bdce62c0ed096ebcce1750d3bd609331f7db2435d73d9a7f228b26c49ca/AmqpConnector-0.0.41.tar.gz +BuildArch: noarch + + +%description +# AmqpConnector + +This is a very minimal library intended for distributed task systems, where the +AMQP system is used for both task distribution, *and* collation of the task +results. This seems to be somewhat unusual among most AMQP libraries, where +a AMQP client is either a pure producer, a pure consumer, or includes everything +including the kitchen sink, a stove, a backup kitchen sink, and possibly +an entire house in case you don't have one to put the sink in (*cough* Celery +*cough*). In this case, each client consumes from one queue, and produces on +another. + +At it's core, this basically just allows one to put byte-strings into one end, +they're passed out to the clients, and the clients then return byte-strings, +which come out the other end. + +Correlation between submitted tasks and responses is entirely left up to the +responsibility of the end-user code. + +Requires: + + - `amqp` library + +%package -n python3-AmqpConnector +Summary: Simple library for building a distributed task system over AMQP. +Provides: python-AmqpConnector +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-AmqpConnector +# AmqpConnector + +This is a very minimal library intended for distributed task systems, where the +AMQP system is used for both task distribution, *and* collation of the task +results. This seems to be somewhat unusual among most AMQP libraries, where +a AMQP client is either a pure producer, a pure consumer, or includes everything +including the kitchen sink, a stove, a backup kitchen sink, and possibly +an entire house in case you don't have one to put the sink in (*cough* Celery +*cough*). In this case, each client consumes from one queue, and produces on +another. + +At it's core, this basically just allows one to put byte-strings into one end, +they're passed out to the clients, and the clients then return byte-strings, +which come out the other end. + +Correlation between submitted tasks and responses is entirely left up to the +responsibility of the end-user code. + +Requires: + + - `amqp` library + +%package help +Summary: Development documents and examples for AmqpConnector +Provides: python3-AmqpConnector-doc +%description help +# AmqpConnector + +This is a very minimal library intended for distributed task systems, where the +AMQP system is used for both task distribution, *and* collation of the task +results. This seems to be somewhat unusual among most AMQP libraries, where +a AMQP client is either a pure producer, a pure consumer, or includes everything +including the kitchen sink, a stove, a backup kitchen sink, and possibly +an entire house in case you don't have one to put the sink in (*cough* Celery +*cough*). In this case, each client consumes from one queue, and produces on +another. + +At it's core, this basically just allows one to put byte-strings into one end, +they're passed out to the clients, and the clients then return byte-strings, +which come out the other end. + +Correlation between submitted tasks and responses is entirely left up to the +responsibility of the end-user code. + +Requires: + + - `amqp` library + +%prep +%autosetup -n AmqpConnector-0.0.41 + +%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-AmqpConnector -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Mon May 29 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.41-1 +- Package Spec generated |