From: Maxime Devos <maximedevos@telenet.be>
To: Tobias Geerinckx-Rice <me@tobias.gr>, "(" <paren@disroot.org>
Cc: 56852@debbugs.gnu.org
Subject: [bug#56852] [PATCH] gnu: Add exult.
Date: Sun, 31 Jul 2022 16:31:31 +0200 [thread overview]
Message-ID: <b61e92bb-950d-ff7e-a040-9469651f01e5@telenet.be> (raw)
In-Reply-To: <87ilndxvd5@nckx>
[-- Attachment #1.1.1: Type: text/plain, Size: 743 bytes --]
On 31-07-2022 15:26, Tobias Geerinckx-Rice via Guix-patches via wrote:
> I'm not sure we ever reached consensus on preferring Git? I'm pro-git
> myself, but if there's consensus we should advertise it more prominently.
I am not aware of a consensus on preferring Git, but using Git had been
noted to be a convenient method for avoiding Autotools binaries (*) and
building from source (*).
However, that's not directly relevant here, as (IIUC your comment
correctly) in this case, the tarball doesn't contain those Autotools
binaries.
Greetings,
Maxime
(*) in the sense used by the GPL and referred to by explanations of '4
freedoms', not in the 'input/output to C compiler / shell interpreter /
...' sense.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-31 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 10:46 [bug#56852] [PATCH] gnu: Add exult Tobias Geerinckx-Rice via Guix-patches via
2022-07-31 11:52 ` ( via Guix-patches via
2022-07-31 13:26 ` Tobias Geerinckx-Rice via Guix-patches via
2022-07-31 13:41 ` ( via Guix-patches via
2022-07-31 14:31 ` Maxime Devos [this message]
2022-07-31 14:23 ` ( via Guix-patches via
2022-08-12 19:46 ` Tobias Geerinckx-Rice via Guix-patches via
2023-09-02 3:38 ` bug#56852: " Vagrant Cascadian
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b61e92bb-950d-ff7e-a040-9469651f01e5@telenet.be \
--to=maximedevos@telenet.be \
--cc=56852@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=paren@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).