automatic import of python-licant

1 files changed, 87 insertions, 0 deletions

diff --git a/python-licant.spec b/python-licant.spec
new file mode 100644
index 0000000..f37624d
--- /dev/null
+++ b/python-licant.spec
@@ -0,0 +1,87 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-licant
+Version:	1.15.0
+Release:	1
+Summary:	licant make system
+License:	MIT
+URL:		https://github.com/mirmik/licant
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/04/58/be05fc0d880bd33e4c1bd626e1828c744b02a73c28a860f6c75a72d1133a/licant-1.15.0.tar.gz
+BuildArch:	noarch
+
+
+%description
+Initially Likant was written as a system for assembling code for projects on microcontrollers.
+The core of the Lycant system is a make-like assembly tree solver written in python.
+But, the main feature of Licant in the system of modules.
+The Likant paradigm consists in the description of a project by a set of modules that link to each other. Connecting the module automatically tightens the connection of dependent modules.
+Modules can have several implementations, which allows flexible configuration of the project. (For example, you can change the initialization code of the microcontroller or the implementation of the input-output system simply by replacing the implementation of the corresponding module).
+One of the goals of the project is to work with submodules located in remote directories. The library subsystem allows a project to refer to modules located in remote directories, which allows several projects to use the same code.
+
+%package -n python3-licant
+Summary:	licant make system
+Provides:	python-licant
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-licant
+Initially Likant was written as a system for assembling code for projects on microcontrollers.
+The core of the Lycant system is a make-like assembly tree solver written in python.
+But, the main feature of Licant in the system of modules.
+The Likant paradigm consists in the description of a project by a set of modules that link to each other. Connecting the module automatically tightens the connection of dependent modules.
+Modules can have several implementations, which allows flexible configuration of the project. (For example, you can change the initialization code of the microcontroller or the implementation of the input-output system simply by replacing the implementation of the corresponding module).
+One of the goals of the project is to work with submodules located in remote directories. The library subsystem allows a project to refer to modules located in remote directories, which allows several projects to use the same code.
+
+%package help
+Summary:	Development documents and examples for licant
+Provides:	python3-licant-doc
+%description help
+Initially Likant was written as a system for assembling code for projects on microcontrollers.
+The core of the Lycant system is a make-like assembly tree solver written in python.
+But, the main feature of Licant in the system of modules.
+The Likant paradigm consists in the description of a project by a set of modules that link to each other. Connecting the module automatically tightens the connection of dependent modules.
+Modules can have several implementations, which allows flexible configuration of the project. (For example, you can change the initialization code of the microcontroller or the implementation of the input-output system simply by replacing the implementation of the corresponding module).
+One of the goals of the project is to work with submodules located in remote directories. The library subsystem allows a project to refer to modules located in remote directories, which allows several projects to use the same code.
+
+%prep
+%autosetup -n licant-1.15.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-licant -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Thu May 18 2023 Python_Bot <Python_Bot@openeuler.org> - 1.15.0-1
+- Package Spec generated