From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: new package: pypy3.7
Date: Thu, 16 Dec 2021 04:06:25 +0100 [thread overview]
Message-ID: <20211216030625.JeEDAmIb3PJ4hrS2s4jZrN0kT9fjSKrgujMhJKiIIQ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33712@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/33712#issuecomment-995397285
Comment:
Self-referential cycles are not an option because it will break the dependency resolver and, even if it didn't, our policy requires that all packages in the repo be buildable without requiring specific pre-existing repo state. (This is an ideal, and some package changes can sometimes lead to violations of this policy, but we don't knowingly permit it.)
I can be persuaded that building a temporary cpython 2.7 in pre_build to bootstrap native pypy is reasonable option. That's not much different than how we (were, before py3.10) bootstrapping `python3` on cross builds.
Practically, because the python 2.7 package isn't going anywhere for awhile, maybe it suffices to know that we *can* build a cpython bootstrap in the template if we ever need to; just pulling the python package in hostmakedepends might be OK for now after all.
I'm not sure if using native pypy to bootstrap cross pypy is better than *always* using (and, in the future, potentially building) native cpython. Arguments on either side would be appreciated.
Of course, we can always hope that pypy solves the bootstrap problem before we have to...
next prev parent reply other threads:[~2021-12-16 3:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 13:07 [PR PATCH] " dkwo
2021-10-23 13:19 ` [PR REVIEW] " Chocimier
2021-10-23 13:19 ` Chocimier
2021-10-23 15:27 ` dkwo
2021-10-23 16:34 ` [PR PATCH] [Updated] " dkwo
2021-10-26 9:03 ` dkwo
2021-10-26 18:41 ` Chocimier
2021-10-26 18:42 ` [PR REVIEW] " Chocimier
2021-10-26 18:42 ` Chocimier
2021-10-27 9:50 ` [PR PATCH] [Updated] " dkwo
2021-10-27 9:51 ` [PR REVIEW] " dkwo
2021-10-27 19:05 ` [PR PATCH] [Updated] " dkwo
2021-10-28 11:40 ` dkwo
2021-10-28 11:42 ` dkwo
2021-12-16 0:51 ` EliteTK
2021-12-16 1:01 ` ahesford
2021-12-16 2:32 ` EliteTK
2021-12-16 2:33 ` EliteTK
2021-12-16 3:06 ` ahesford [this message]
2021-12-16 9:04 ` dkwo
2022-01-02 8:34 ` dkwo
2022-01-02 8:34 ` [PR PATCH] [Closed]: " dkwo
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=20211216030625.JeEDAmIb3PJ4hrS2s4jZrN0kT9fjSKrgujMhJKiIIQ8@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).