From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Support for PEP517 build systems in python3-module
Date: Wed, 02 Dec 2020 20:59:46 +0100 [thread overview]
Message-ID: <20201202195946.-KYOAafw1eJWfJtAU___1UzTLA9j9mdrnFIXpzsQsyI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26883@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/26883#issuecomment-737461829
Comment:
On 2020-12-02 at 14:43 (UTC -0500), John Zimmermann wrote:
> Why not do it as a seperate build_style? I would see it as a totally
> different build system and therefore it also should be in it's own
> build_style, especially since it already doesn't do it automatically
> but you need to manually set a var.
I don't oppose splitting this into a separate build style. Are there
arguments against doing so?
If it does become its own style, any thoughts on the name? An obvious
choice is `python3-pep517`, but we could also go for something like
`python3-wheel` if "pep517" seems like inside baseball.
next prev parent reply other threads:[~2020-12-02 19:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 16:00 [PR PATCH] " ahesford
2020-12-02 17:45 ` [PR REVIEW] " ericonr
2020-12-02 19:02 ` [PR PATCH] [Updated] " ahesford
2020-12-02 19:06 ` [PR REVIEW] " ahesford
2020-12-02 19:10 ` ericonr
2020-12-02 19:11 ` ericonr
2020-12-02 19:14 ` ericonr
2020-12-02 19:27 ` [PR PATCH] [Updated] " ahesford
2020-12-02 19:28 ` [PR REVIEW] " ahesford
2020-12-02 19:30 ` [PR PATCH] [Updated] " ahesford
2020-12-02 19:42 ` Johnnynator
2020-12-02 19:59 ` ahesford [this message]
2020-12-02 20:21 ` [PR REVIEW] " Chocimier
2020-12-02 23:37 ` fosslinux
2020-12-03 3:43 ` [PR PATCH] [Updated] " ahesford
2020-12-03 3:52 ` ahesford
2020-12-05 16:29 ` [RFC] Support for PEP517 build systems with new build style Chocimier
2020-12-06 5:48 ` [PR PATCH] [Updated] " ahesford
2020-12-06 5:53 ` ahesford
2020-12-06 5:56 ` ahesford
2020-12-06 5:56 ` ahesford
2020-12-08 20:57 ` ahesford
2020-12-08 20:57 ` [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=20201202195946.-KYOAafw1eJWfJtAU___1UzTLA9j9mdrnFIXpzsQsyI@z \
--to=ahesford@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).