From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] Add vtargetrun (run executables with qemu) and vcompletion (install helper for shell completions); use them in rustup and starship
Date: Mon, 20 Jul 2020 17:26:43 +0200 [thread overview]
Message-ID: <20200720152643.43-17DlDqwxAEfbMS3FbncBfHRZuVp3x5yUH2HG77xk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22785@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
New review comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/22785#discussion_r457492998
Comment:
I wouldn't go too crazy here. If you try building for archs that don't have binary packages, you are going to go crazy building a bunch of stuff just to get to the point where you can test your package. The main idea should be to prevent issues with trying to build official binary packages. If somebody wants to try building rustup for mips, let the user with the problem get involved with resolving any problems that shake out.
next prev parent reply other threads:[~2020-07-20 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22785@inbox.vuxu.org>
2020-07-08 19:37 ` ericonr
2020-07-08 22:17 ` jcgruenhage
2020-07-20 3:36 ` [PR PATCH] [Updated] " ericonr
2020-07-20 4:04 ` ericonr
2020-07-20 4:45 ` ericonr
2020-07-20 5:22 ` [PR REVIEW] " fosslinux
2020-07-20 5:22 ` fosslinux
2020-07-20 13:52 ` ericonr
2020-07-20 15:26 ` ahesford [this message]
2020-07-20 15:46 ` ahesford
2020-07-20 18:51 ` [PR PATCH] [Updated] " ericonr
2020-07-20 19:06 ` [PR REVIEW] " ahesford
2020-07-20 19:12 ` ericonr
2020-07-21 2:09 ` fosslinux
2020-07-28 2:43 ` [PR PATCH] [Updated] " ericonr
2020-07-28 2:51 ` ericonr
2020-07-28 4:24 ` [PR PATCH] [Merged]: " sgn
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=20200720152643.43-17DlDqwxAEfbMS3FbncBfHRZuVp3x5yUH2HG77xk@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).