From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: new package: pypy3.7
Date: Thu, 16 Dec 2021 02:01:38 +0100 [thread overview]
Message-ID: <20211216010138.4JrzuLoCvsAMzWOveMF9KB_g47jPB04h-03c7BvUkEQ@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: 1186 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/33712#issuecomment-995344022
Comment:
All of these options looks have serious drawbacks. Using native, precompiled binaries to bootstrap another arch is bad because it forces us to cross compile those archs. In Void, cross compilation is an incidental implementation detail of architectures for which we can't afford or don't want to maintain build infrastructure. It should always be possible to natively build any of our archs if one is so inclined, but the precompiled pypy bootstrap breaks this.
Relying on dead cpython is also lousy. We want to get rid of the package, not force it closer to the root of the dependency tree.
If we are going to overlook this catch-22, I would prefer to avoid another cpython2 dependency. I would also like to avoid creating some new package that only exists to build pypy. The best way out, if possible, would be to fetch the prebuilt distribution for native builds as another distfile. Use the locally extracted copy to build the packaged version. For cross builds, this can go away and we just pull the native pypy into hostmakedepends.
next prev parent reply other threads:[~2021-12-16 1:01 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 [this message]
2021-12-16 2:32 ` EliteTK
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=20211216010138.4JrzuLoCvsAMzWOveMF9KB_g47jPB04h-03c7BvUkEQ@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).