diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-data-repo-client.spec | 82 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 84 insertions, 0 deletions
@@ -0,0 +1 @@ +/data-repo-client-1.478.0.tar.gz diff --git a/python-data-repo-client.spec b/python-data-repo-client.spec new file mode 100644 index 0000000..2562e32 --- /dev/null +++ b/python-data-repo-client.spec @@ -0,0 +1,82 @@ +%global _empty_manifest_terminate_build 0 +Name: python-data-repo-client +Version: 1.478.0 +Release: 1 +Summary: Data Repository API +License: Apache 2.0 +URL: https://pypi.org/project/data-repo-client/ +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/37/c3/aff55441cba10eac102d3e7cc5684570657aded0612a30d16c9e9b5b0f06/data-repo-client-1.478.0.tar.gz +BuildArch: noarch + +Requires: python3-urllib3 +Requires: python3-six +Requires: python3-certifi +Requires: python3-dateutil + +%description + <details><summary>This document defines the REST API for the Terra Data Repository.</summary> <p> **Status: design in progress** There are a few top-level endpoints (besides some used by swagger): * / - generated by swagger: swagger API page that provides this documentation and a live UI for submitting REST requests * /status - provides the operational status of the service * /configuration - provides the basic configuration and information about the service * /api - is the authenticated and authorized Data Repository API * /ga4gh/drs/v1 - is a transcription of the Data Repository Service API The API endpoints are organized by interface. Each interface is separately versioned. <p> **Notes on Naming** <p> All of the reference items are suffixed with \\"Model\\". Those names are used as the class names in the generated Java code. It is helpful to distinguish these model classes from other related classes, like the DAO classes and the operation classes. </details> # noqa: E501 + + + +%package -n python3-data-repo-client +Summary: Data Repository API +Provides: python-data-repo-client +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-data-repo-client + <details><summary>This document defines the REST API for the Terra Data Repository.</summary> <p> **Status: design in progress** There are a few top-level endpoints (besides some used by swagger): * / - generated by swagger: swagger API page that provides this documentation and a live UI for submitting REST requests * /status - provides the operational status of the service * /configuration - provides the basic configuration and information about the service * /api - is the authenticated and authorized Data Repository API * /ga4gh/drs/v1 - is a transcription of the Data Repository Service API The API endpoints are organized by interface. Each interface is separately versioned. <p> **Notes on Naming** <p> All of the reference items are suffixed with \\"Model\\". Those names are used as the class names in the generated Java code. It is helpful to distinguish these model classes from other related classes, like the DAO classes and the operation classes. </details> # noqa: E501 + + + +%package help +Summary: Development documents and examples for data-repo-client +Provides: python3-data-repo-client-doc +%description help + <details><summary>This document defines the REST API for the Terra Data Repository.</summary> <p> **Status: design in progress** There are a few top-level endpoints (besides some used by swagger): * / - generated by swagger: swagger API page that provides this documentation and a live UI for submitting REST requests * /status - provides the operational status of the service * /configuration - provides the basic configuration and information about the service * /api - is the authenticated and authorized Data Repository API * /ga4gh/drs/v1 - is a transcription of the Data Repository Service API The API endpoints are organized by interface. Each interface is separately versioned. <p> **Notes on Naming** <p> All of the reference items are suffixed with \\"Model\\". Those names are used as the class names in the generated Java code. It is helpful to distinguish these model classes from other related classes, like the DAO classes and the operation classes. </details> # noqa: E501 + + + +%prep +%autosetup -n data-repo-client-1.478.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-data-repo-client -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.478.0-1 +- Package Spec generated @@ -0,0 +1 @@ +d63f1daf4fba26eda7dddb6bba2bc2ef data-repo-client-1.478.0.tar.gz |