automatic import of python-aistac-foundation

3 files changed, 164 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..eac99ea 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/aistac-foundation-2.13.7.tar.gz
diff --git a/python-aistac-foundation.spec b/python-aistac-foundation.spec
new file mode 100644
index 0000000..531544c
--- /dev/null
+++ b/python-aistac-foundation.spec
@@ -0,0 +1,162 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-aistac-foundation
+Version:	2.13.7
+Release:	1
+Summary:	Augmented Intent Single Task Adaptive Components
+License:	BSD
+URL:		http://github.com/gigas64/aistac-foundation
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/88/03/706ff2f62ca90c877b65e705c90fd256a2accad2b0b32b77aa8f4763f447/aistac-foundation-2.13.7.tar.gz
+BuildArch:	noarch
+
+
+%description
+Project Hadron provides a clear separation of concerns between components and their actions and data
+and its content, whilst maintaining the original intentions of the data scientist, that can be passed
+to a production team. It offers trust between the data scientists teams and product teams. It brings
+with it transparency and traceability, dealing with bias, fairness, and knowledge. The resulting
+outcome provides the product engineers with adaptability, robustness, and reuse; fitting seamlessly
+into a microservices solution that can be language agnostic.
+Project Hadron is designed using Microservices. Microservices - also known as the microservice
+architecture - is an architectural pattern that structures an application as a collection of
+component services that are:
+* Highly maintainable and testable
+* Loosely coupled
+* Independently deployable
+* Highly reusable
+* Resilient
+* Technically independent
+Component services are built for business capabilities and each service performs a single function.
+Because they are independently run, each service can be updated, deployed, and scaled to meet demand
+for specific functions of an application. Project Hadron microservices enable the rapid, frequent
+and reliable delivery of large, complex applications. It also enables an organization to evolve its
+technology stack and experiment with innovative ideas.
+At the heart of Project Hadron is a multi-tenant, NoSQL, singleton, in memory data store that has
+minimal code and functionality and has been custom built specifically for Hadron tasks in  mind.
+Abstracted from this is the component store which allows us to build a reusable set of methods
+that define each tenanted component that sits separately from the store itself. In addition, a
+dynamic key value class provides labeling so that each tenant is not tied to a fixed set of
+reference values unless by specificity. Each of the classes, the data store, the component
+property manager, and the key value pairs that make up the component are all independent,
+giving complete flexibility and minimum code footprint to the build process of new components.
+This is what gives us the Domain Contract for each tenant which sits at the heart of what makes
+the contracts reusable, translatable, transferable and brings the data scientist closer to the
+production engineer along with building a production ready component solution.
+
+%package -n python3-aistac-foundation
+Summary:	Augmented Intent Single Task Adaptive Components
+Provides:	python-aistac-foundation
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-aistac-foundation
+Project Hadron provides a clear separation of concerns between components and their actions and data
+and its content, whilst maintaining the original intentions of the data scientist, that can be passed
+to a production team. It offers trust between the data scientists teams and product teams. It brings
+with it transparency and traceability, dealing with bias, fairness, and knowledge. The resulting
+outcome provides the product engineers with adaptability, robustness, and reuse; fitting seamlessly
+into a microservices solution that can be language agnostic.
+Project Hadron is designed using Microservices. Microservices - also known as the microservice
+architecture - is an architectural pattern that structures an application as a collection of
+component services that are:
+* Highly maintainable and testable
+* Loosely coupled
+* Independently deployable
+* Highly reusable
+* Resilient
+* Technically independent
+Component services are built for business capabilities and each service performs a single function.
+Because they are independently run, each service can be updated, deployed, and scaled to meet demand
+for specific functions of an application. Project Hadron microservices enable the rapid, frequent
+and reliable delivery of large, complex applications. It also enables an organization to evolve its
+technology stack and experiment with innovative ideas.
+At the heart of Project Hadron is a multi-tenant, NoSQL, singleton, in memory data store that has
+minimal code and functionality and has been custom built specifically for Hadron tasks in  mind.
+Abstracted from this is the component store which allows us to build a reusable set of methods
+that define each tenanted component that sits separately from the store itself. In addition, a
+dynamic key value class provides labeling so that each tenant is not tied to a fixed set of
+reference values unless by specificity. Each of the classes, the data store, the component
+property manager, and the key value pairs that make up the component are all independent,
+giving complete flexibility and minimum code footprint to the build process of new components.
+This is what gives us the Domain Contract for each tenant which sits at the heart of what makes
+the contracts reusable, translatable, transferable and brings the data scientist closer to the
+production engineer along with building a production ready component solution.
+
+%package help
+Summary:	Development documents and examples for aistac-foundation
+Provides:	python3-aistac-foundation-doc
+%description help
+Project Hadron provides a clear separation of concerns between components and their actions and data
+and its content, whilst maintaining the original intentions of the data scientist, that can be passed
+to a production team. It offers trust between the data scientists teams and product teams. It brings
+with it transparency and traceability, dealing with bias, fairness, and knowledge. The resulting
+outcome provides the product engineers with adaptability, robustness, and reuse; fitting seamlessly
+into a microservices solution that can be language agnostic.
+Project Hadron is designed using Microservices. Microservices - also known as the microservice
+architecture - is an architectural pattern that structures an application as a collection of
+component services that are:
+* Highly maintainable and testable
+* Loosely coupled
+* Independently deployable
+* Highly reusable
+* Resilient
+* Technically independent
+Component services are built for business capabilities and each service performs a single function.
+Because they are independently run, each service can be updated, deployed, and scaled to meet demand
+for specific functions of an application. Project Hadron microservices enable the rapid, frequent
+and reliable delivery of large, complex applications. It also enables an organization to evolve its
+technology stack and experiment with innovative ideas.
+At the heart of Project Hadron is a multi-tenant, NoSQL, singleton, in memory data store that has
+minimal code and functionality and has been custom built specifically for Hadron tasks in  mind.
+Abstracted from this is the component store which allows us to build a reusable set of methods
+that define each tenanted component that sits separately from the store itself. In addition, a
+dynamic key value class provides labeling so that each tenant is not tied to a fixed set of
+reference values unless by specificity. Each of the classes, the data store, the component
+property manager, and the key value pairs that make up the component are all independent,
+giving complete flexibility and minimum code footprint to the build process of new components.
+This is what gives us the Domain Contract for each tenant which sits at the heart of what makes
+the contracts reusable, translatable, transferable and brings the data scientist closer to the
+production engineer along with building a production ready component solution.
+
+%prep
+%autosetup -n aistac-foundation-2.13.7
+
+%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-aistac-foundation -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 2.13.7-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..5909336
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+ff64950f413d40edf2d19edea26a1a37  aistac-foundation-2.13.7.tar.gz