automatic import of python-poetry-core

3 files changed, 210 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..5567cdc 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/poetry_core-1.5.1.tar.gz
diff --git a/python-poetry-core.spec b/python-poetry-core.spec
new file mode 100644
index 0000000..43c59a8
--- /dev/null
+++ b/python-poetry-core.spec
@@ -0,0 +1,208 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-poetry-core
+Version:	1.5.1
+Release:	1
+Summary:	Poetry PEP 517 Build Backend
+License:	MIT
+URL:		https://github.com/python-poetry/poetry-core
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/69/52/b73aade26e2487159ad2c1b5fd7cd2b76532e146dd36f99b4be4f741b13b/poetry_core-1.5.1.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-importlib-metadata
+
+%description
+# Poetry Core
+[![PyPI version](https://img.shields.io/pypi/v/poetry-core)](https://pypi.org/project/poetry-core/)
+[![Python Versions](https://img.shields.io/pypi/pyversions/poetry-core)](https://pypi.org/project/poetry-core/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
+[![](https://github.com/python-poetry/poetry-core/workflows/Tests/badge.svg)](https://github.com/python-poetry/poetry-core/actions?query=workflow%3ATests)
+
+A [PEP 517](https://www.python.org/dev/peps/pep-0517/) build backend implementation developed for
+[Poetry](https://github.com/python-poetry/poetry). This project is intended to be a light weight, fully compliant,
+self-contained package allowing PEP 517 compatible build frontends to build Poetry managed projects.
+
+## Usage
+In most cases, the usage of this package is transparent to the end-user as it is either made use by Poetry itself
+or a PEP 517 frontend (eg: `pip`).
+
+In order to enable the use `poetry-core` as your build backend, the following snippet must be present in your
+project's `pyproject.toml` file.
+
+```toml
+[build-system]
+requires = ["poetry-core"]
+build-backend = "poetry.core.masonry.api"
+```
+
+Once this is present, a PEP 517 frontend like `pip` can build and install your project from source without the need
+for Poetry or any of its dependencies.
+
+```shell
+# install to current environment
+pip install /path/to/poetry/managed/project
+
+# build a wheel package
+pip wheel /path/to/poetry/managed/project
+```
+
+## Why is this required?
+Prior to the release of version `1.1.0`, Poetry was a project management tool that included a PEP 517
+build backend. This was inefficient and time consuming when a PEP 517 build was required. For example,
+both `pip` and `tox` (with isolated builds) would install Poetry and all dependencies it required. Most of these
+dependencies are not required when the objective is to simply build either a source or binary distribution of your
+project.
+
+In order to improve the above situation, `poetry-core` was created. Shared functionality pertaining to PEP 517 build
+backends, including reading lock file, `pyproject.toml` and building wheel/sdist, were implemented in this package. This
+makes PEP 517 builds extremely fast for Poetry managed packages.
+
+
+%package -n python3-poetry-core
+Summary:	Poetry PEP 517 Build Backend
+Provides:	python-poetry-core
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-poetry-core
+# Poetry Core
+[![PyPI version](https://img.shields.io/pypi/v/poetry-core)](https://pypi.org/project/poetry-core/)
+[![Python Versions](https://img.shields.io/pypi/pyversions/poetry-core)](https://pypi.org/project/poetry-core/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
+[![](https://github.com/python-poetry/poetry-core/workflows/Tests/badge.svg)](https://github.com/python-poetry/poetry-core/actions?query=workflow%3ATests)
+
+A [PEP 517](https://www.python.org/dev/peps/pep-0517/) build backend implementation developed for
+[Poetry](https://github.com/python-poetry/poetry). This project is intended to be a light weight, fully compliant,
+self-contained package allowing PEP 517 compatible build frontends to build Poetry managed projects.
+
+## Usage
+In most cases, the usage of this package is transparent to the end-user as it is either made use by Poetry itself
+or a PEP 517 frontend (eg: `pip`).
+
+In order to enable the use `poetry-core` as your build backend, the following snippet must be present in your
+project's `pyproject.toml` file.
+
+```toml
+[build-system]
+requires = ["poetry-core"]
+build-backend = "poetry.core.masonry.api"
+```
+
+Once this is present, a PEP 517 frontend like `pip` can build and install your project from source without the need
+for Poetry or any of its dependencies.
+
+```shell
+# install to current environment
+pip install /path/to/poetry/managed/project
+
+# build a wheel package
+pip wheel /path/to/poetry/managed/project
+```
+
+## Why is this required?
+Prior to the release of version `1.1.0`, Poetry was a project management tool that included a PEP 517
+build backend. This was inefficient and time consuming when a PEP 517 build was required. For example,
+both `pip` and `tox` (with isolated builds) would install Poetry and all dependencies it required. Most of these
+dependencies are not required when the objective is to simply build either a source or binary distribution of your
+project.
+
+In order to improve the above situation, `poetry-core` was created. Shared functionality pertaining to PEP 517 build
+backends, including reading lock file, `pyproject.toml` and building wheel/sdist, were implemented in this package. This
+makes PEP 517 builds extremely fast for Poetry managed packages.
+
+
+%package help
+Summary:	Development documents and examples for poetry-core
+Provides:	python3-poetry-core-doc
+%description help
+# Poetry Core
+[![PyPI version](https://img.shields.io/pypi/v/poetry-core)](https://pypi.org/project/poetry-core/)
+[![Python Versions](https://img.shields.io/pypi/pyversions/poetry-core)](https://pypi.org/project/poetry-core/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
+[![](https://github.com/python-poetry/poetry-core/workflows/Tests/badge.svg)](https://github.com/python-poetry/poetry-core/actions?query=workflow%3ATests)
+
+A [PEP 517](https://www.python.org/dev/peps/pep-0517/) build backend implementation developed for
+[Poetry](https://github.com/python-poetry/poetry). This project is intended to be a light weight, fully compliant,
+self-contained package allowing PEP 517 compatible build frontends to build Poetry managed projects.
+
+## Usage
+In most cases, the usage of this package is transparent to the end-user as it is either made use by Poetry itself
+or a PEP 517 frontend (eg: `pip`).
+
+In order to enable the use `poetry-core` as your build backend, the following snippet must be present in your
+project's `pyproject.toml` file.
+
+```toml
+[build-system]
+requires = ["poetry-core"]
+build-backend = "poetry.core.masonry.api"
+```
+
+Once this is present, a PEP 517 frontend like `pip` can build and install your project from source without the need
+for Poetry or any of its dependencies.
+
+```shell
+# install to current environment
+pip install /path/to/poetry/managed/project
+
+# build a wheel package
+pip wheel /path/to/poetry/managed/project
+```
+
+## Why is this required?
+Prior to the release of version `1.1.0`, Poetry was a project management tool that included a PEP 517
+build backend. This was inefficient and time consuming when a PEP 517 build was required. For example,
+both `pip` and `tox` (with isolated builds) would install Poetry and all dependencies it required. Most of these
+dependencies are not required when the objective is to simply build either a source or binary distribution of your
+project.
+
+In order to improve the above situation, `poetry-core` was created. Shared functionality pertaining to PEP 517 build
+backends, including reading lock file, `pyproject.toml` and building wheel/sdist, were implemented in this package. This
+makes PEP 517 builds extremely fast for Poetry managed packages.
+
+
+%prep
+%autosetup -n poetry-core-1.5.1
+
+%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-poetry-core -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 1.5.1-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..dfc822f
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+dd3b6990ef6608bd477a1727a4e72d4f  poetry_core-1.5.1.tar.gz