From: EliteTK <EliteTK@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: new package: pypy3.7
Date: Thu, 16 Dec 2021 03:32:24 +0100 [thread overview]
Message-ID: <20211216023224.MJXbCc5AouuwdHOMiQ8LshxuyE06mu7MUT_sLI2K2Po@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: 950 bytes --]
New comment by EliteTK on void-packages repository
https://github.com/void-linux/void-packages/pull/33712#issuecomment-995384130
Comment:
Some distros take the self-referential approach of just making pypy depend on itself for every build. Where at some point in the past they had some bootstrap package which was either an upstream binary or a cpython2 build of pypy which was then used to kickstart the ouroboros in perpetuity. Would this be an option? (Apparently, alpine and maybe archlinux did this.)
Alternatively, it's possible to have the pypy package have cpython2 sources in the distfiles instead of the upstream pypy and build that to then have the pypy package first build cpython2 and then pypy. This would avoid having an official cpython2 package and I think this is certainly a lot more transparent than using the upstream pypy.
@dkwo are you still interested in getting this working? If not, I can try to pick up the effort.
next prev parent reply other threads:[~2021-12-16 2:32 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 [this message]
2021-12-16 2:33 ` EliteTK
2021-12-16 3:06 ` ahesford
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=20211216023224.MJXbCc5AouuwdHOMiQ8LshxuyE06mu7MUT_sLI2K2Po@z \
--to=elitetk@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).