From: TeddyDD <TeddyDD@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lf: build with cgo=0, run checks
Date: Wed, 31 Jan 2024 19:44:25 +0100 [thread overview]
Message-ID: <20240131184425.760AD22E76@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48373@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
New comment by TeddyDD on void-packages repository
https://github.com/void-linux/void-packages/pull/48373#issuecomment-1919718531
Comment:
> That's what upstream does and suggests
It's not a strong suggestion, just copy-paste instruction for people who want to build it from source.
Half of programs written in Go suggest you should do static build so you can copy binary around.
For whatever reason, Void doesn't do this, and I fell like exceptions shoud be justified.
next prev parent reply other threads:[~2024-01-31 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 21:45 [PR PATCH] " dkwo
2024-01-26 7:42 ` TeddyDD
2024-01-30 22:48 ` dkwo
2024-01-31 18:44 ` TeddyDD [this message]
2024-01-31 21:17 ` [PR PATCH] [Closed]: " dkwo
2024-01-31 21:17 ` 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=20240131184425.760AD22E76@inbox.vuxu.org \
--to=teddydd@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).