automatic import of python-dm-xmlsec-binding

1 files changed, 129 insertions, 0 deletions

diff --git a/python-dm-xmlsec-binding.spec b/python-dm-xmlsec-binding.spec
new file mode 100644
index 0000000..d536aaf
--- /dev/null
+++ b/python-dm-xmlsec-binding.spec
@@ -0,0 +1,129 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-dm.xmlsec.binding
+Version:	2.2
+Release:	1
+Summary:	Cython/lxml based binding for the XML security library -- for lxml 3.x
+License:	BSD
+URL:		https://pypi.org/project/dm.xmlsec.binding
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/5d/48/5e0af5cd9dfc250b784548cd85a14551f173ef4fa1f9b47595b7e5c09557/dm.xmlsec.binding-2.2.tar.gz
+BuildArch:	noarch
+
+
+%description
+Installation of this package requires that you have previously installed
+`setuptools` (http://pypi.python.org/pypi/setuptools) or an equivalent
+package manager.
+In addition, you must have installed the development packages for
+libxml2 and the XML security library (often called ``libxmlsec1``)
+on the operating system level.
+The installation will install ``lxml``, if not yet already installed.
+This package interfaces with ``lxml`` via its Cython interface
+(described in ``etreepublic.pxd``). Some operating system installations
+for ``lxml`` lack the respective files. In those cases, you may need to
+download an `lxml` source distribution and let the environment
+variable ``LXML_HOME`` point to its root.
+``xmlsec`` can use different cryptographic engines (currently ``openssl``,
+``gnutls`` and ``nss``). By default, this package configures
+``xmlsec`` to use its default engine. Should you require a different
+engine, you can set the envvar ``XMLSEC_CRYPTO_ENGINE`` to the corresponding
+value. In this case, you may need to pass the name of your crypto engine
+to the ``initialize`` function.
+I have tried installation only on Linux, it may not work on other
+platforms.
+
+%package -n python3-dm.xmlsec.binding
+Summary:	Cython/lxml based binding for the XML security library -- for lxml 3.x
+Provides:	python-dm.xmlsec.binding
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-dm.xmlsec.binding
+Installation of this package requires that you have previously installed
+`setuptools` (http://pypi.python.org/pypi/setuptools) or an equivalent
+package manager.
+In addition, you must have installed the development packages for
+libxml2 and the XML security library (often called ``libxmlsec1``)
+on the operating system level.
+The installation will install ``lxml``, if not yet already installed.
+This package interfaces with ``lxml`` via its Cython interface
+(described in ``etreepublic.pxd``). Some operating system installations
+for ``lxml`` lack the respective files. In those cases, you may need to
+download an `lxml` source distribution and let the environment
+variable ``LXML_HOME`` point to its root.
+``xmlsec`` can use different cryptographic engines (currently ``openssl``,
+``gnutls`` and ``nss``). By default, this package configures
+``xmlsec`` to use its default engine. Should you require a different
+engine, you can set the envvar ``XMLSEC_CRYPTO_ENGINE`` to the corresponding
+value. In this case, you may need to pass the name of your crypto engine
+to the ``initialize`` function.
+I have tried installation only on Linux, it may not work on other
+platforms.
+
+%package help
+Summary:	Development documents and examples for dm.xmlsec.binding
+Provides:	python3-dm.xmlsec.binding-doc
+%description help
+Installation of this package requires that you have previously installed
+`setuptools` (http://pypi.python.org/pypi/setuptools) or an equivalent
+package manager.
+In addition, you must have installed the development packages for
+libxml2 and the XML security library (often called ``libxmlsec1``)
+on the operating system level.
+The installation will install ``lxml``, if not yet already installed.
+This package interfaces with ``lxml`` via its Cython interface
+(described in ``etreepublic.pxd``). Some operating system installations
+for ``lxml`` lack the respective files. In those cases, you may need to
+download an `lxml` source distribution and let the environment
+variable ``LXML_HOME`` point to its root.
+``xmlsec`` can use different cryptographic engines (currently ``openssl``,
+``gnutls`` and ``nss``). By default, this package configures
+``xmlsec`` to use its default engine. Should you require a different
+engine, you can set the envvar ``XMLSEC_CRYPTO_ENGINE`` to the corresponding
+value. In this case, you may need to pass the name of your crypto engine
+to the ``initialize`` function.
+I have tried installation only on Linux, it may not work on other
+platforms.
+
+%prep
+%autosetup -n dm.xmlsec.binding-2.2
+
+%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-dm.xmlsec.binding -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 2.2-1
+- Package Spec generated