From: kwshi <kwshi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: python3-poetry-core-1.0.3
Date: Wed, 28 Apr 2021 22:06:59 +0200 [thread overview]
Message-ID: <20210428200659.laMAABxLG1wfUau6aH_DOic2Ih04_vxOd42yLfG7kZ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30552@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
There is an updated pull request by kwshi against master on the void-packages repository
https://github.com/kwshi/void-packages poetry-core
https://github.com/void-linux/void-packages/pull/30552
New package: python3-poetry-core-1.0.3
- New package: python3-poetry-core
- Manual.md: add instructions for Poetry-built Python packages
<!-- Mark items with [x] where applicable -->
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/30552.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-poetry-core-30552.patch --]
[-- Type: text/x-diff, Size: 2112 bytes --]
From 3c177c05d18a8b34a32f8141cb7646bc96853265 Mon Sep 17 00:00:00 2001
From: Kye Shi <shi.kye@gmail.com>
Date: Tue, 27 Apr 2021 12:11:03 -0700
Subject: [PATCH 1/2] New package: python3-poetry-core-1.0.3
---
srcpkgs/python3-poetry-core/template | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
create mode 100644 srcpkgs/python3-poetry-core/template
diff --git a/srcpkgs/python3-poetry-core/template b/srcpkgs/python3-poetry-core/template
new file mode 100644
index 000000000000..6d4a7c507c90
--- /dev/null
+++ b/srcpkgs/python3-poetry-core/template
@@ -0,0 +1,19 @@
+# Template file for 'python3-poetry-core'
+pkgname=python3-poetry-core
+version=1.0.3
+revision=1
+wrksrc="poetry-core-${version}"
+build_style="python3-module"
+make_install_target="poetry_core-${version}-*-*-*.whl"
+hostmakedepends="python3-wheel"
+depends="python3"
+short_desc="Poetry PEP 517 Build Backend & Core Utilities"
+maintainer="Kye Shi <shi.kye@gmail.com>"
+license="MIT"
+homepage="https://github.com/python-poetry/poetry-core"
+distfiles="${PYPI_SITE}/p/poetry-core/poetry-core-${version}.tar.gz"
+checksum="2315c928249fc3207801a81868b64c66273077b26c8d8da465dccf8f488c90c5"
+
+post_install() {
+ vlicense LICENSE
+}
From 665c078ef67a465024b821bb6936314c9c87ca93 Mon Sep 17 00:00:00 2001
From: Kye Shi <shi.kye@gmail.com>
Date: Tue, 27 Apr 2021 12:50:44 -0700
Subject: [PATCH 2/2] Manual.md: add instructions for PEP 517 Python package
build backends
---
Manual.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Manual.md b/Manual.md
index 73cd9088f9bc..851e4be41bfc 100644
--- a/Manual.md
+++ b/Manual.md
@@ -1546,6 +1546,9 @@ dependencies at build time. If you notice warnings about `EasyInstall` deprecati
present in `${wrksrc}/.eggs` after building the package, then those packages should be added to
`hostmakedepends`.
+The `python3-pep517` build style does not provide a specific build backend, so
+packages will need to add an appropriate backend provider to `hostmakedepends`.
+
The following variables may influence how the python packages are built and configured
at post-install time:
next prev parent reply other threads:[~2021-04-28 20:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 19:56 [PR PATCH] " kwshi
2021-04-27 20:00 ` [PR REVIEW] " ericonr
2021-04-27 20:02 ` [PR PATCH] [Updated] " kwshi
2021-04-27 20:06 ` kwshi
2021-04-27 20:07 ` [PR PATCH] [Updated] " kwshi
2021-04-27 20:20 ` kwshi
2021-04-27 20:33 ` [PR PATCH] [Updated] " kwshi
2021-04-28 19:02 ` [PR REVIEW] " ahesford
2021-04-28 19:02 ` ahesford
2021-04-28 19:13 ` [PR PATCH] [Updated] " kwshi
2021-04-28 19:13 ` [PR REVIEW] " kwshi
2021-04-28 19:14 ` kwshi
2021-04-28 19:14 ` kwshi
2021-04-28 19:18 ` kwshi
2021-04-28 19:27 ` eli-schwartz
2021-04-28 20:06 ` kwshi [this message]
2021-04-28 20:07 ` kwshi
2021-04-30 20:10 ` kwshi
2021-05-19 3:02 ` [PR PATCH] [Closed]: " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210428200659.laMAABxLG1wfUau6aH_DOic2Ih04_vxOd42yLfG7kZ8@z \
--to=kwshi@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).