From: eli-schwartz <eli-schwartz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] Abandon pip in python3-pep517 build style
Date: Tue, 08 Nov 2022 20:18:12 +0100 [thread overview]
Message-ID: <20221108191812.Z0h29GosNMkKMEBBuvM5JYJFgm7K-Ci7-jdYQwbBWlA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40385@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
New comment by eli-schwartz on void-packages repository
https://github.com/void-linux/void-packages/pull/40385#issuecomment-1307715404
Comment:
I still think it's viable to have a flit build style.
Question: is it viable to have `installer` download both an sdist and a wheel, then install the wheel without needing to depend on flit? This would allow flit_core to depend on `installer` instead of pip. In fact it could use its own build style as it will be on its own import path, you'd just need to skip adding an extra copy of flit to the makedepends.
next prev parent reply other threads:[~2022-11-08 19:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 17:38 [PR PATCH] " ahesford
2022-11-08 17:46 ` [PR PATCH] [Updated] " ahesford
2022-11-08 19:18 ` eli-schwartz [this message]
2022-11-08 19:37 ` ahesford
2022-11-08 19:57 ` eli-schwartz
2022-11-08 20:22 ` ahesford
2022-11-08 21:13 ` [PR PATCH] [Updated] " ahesford
2022-11-08 21:14 ` ahesford
2022-11-08 21:51 ` eli-schwartz
2022-11-08 23:06 ` [PR PATCH] [Updated] " ahesford
2022-11-08 23:08 ` ahesford
2022-11-08 23:09 ` ahesford
2022-11-08 23:44 ` [PR REVIEW] " eli-schwartz
2022-11-08 23:44 ` eli-schwartz
2022-11-08 23:52 ` eli-schwartz
2022-11-09 2:31 ` [PR PATCH] [Updated] " ahesford
2022-11-09 2:34 ` [PR REVIEW] " ahesford
2022-11-09 3:15 ` [PR PATCH] [Updated] " ahesford
2022-11-09 4:15 ` [PR REVIEW] " eli-schwartz
2022-11-10 2:24 ` [PR PATCH] [Merged]: " ahesford
2022-11-10 21:50 ` eli-schwartz
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=20221108191812.Z0h29GosNMkKMEBBuvM5JYJFgm7K-Ci7-jdYQwbBWlA@z \
--to=eli-schwartz@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).