From: Maxime Devos <maximedevos@telenet.be>
To: Cees de Groot <cg@evrl.com>
Cc: 54304@debbugs.gnu.org
Subject: [bug#54304] [PATCH] Don't fix git executable location during Elixir build
Date: Wed, 09 Mar 2022 20:45:41 +0100 [thread overview]
Message-ID: <919b8ca66b9548aa0e3cf682b9e293f7ed28b2a8.camel@telenet.be> (raw)
In-Reply-To: <cU5FfmYRpITfhryoKWDl9Fk9O4bHdSY6qH-1r-XoPShMPsucSfjzsg-9qAge_ewWi5mt-hnBlntnc0F7CO1RmSnibVrYdhaEHIMXnoff6xc=@evrl.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Cees de Groot schreef op wo 09-03-2022 om 17:31 [+0000]:
> I think changing the behaviour of a programming language just to be helpful to developers
Developers are users too and users can be developers. Furthermore,
Elixir is an implementation of a programming language, so aren't all
users of Elixir automatically developers?
I'm not sure how exactly Elixir integrates with git but I assume the
integration can be very useful.
Also, this does not change the behaviour of the language, it only
adjusts a detail of the implementation: the error message for
indicating that git is missing is adjusted.
> is something that one may consider for upstream, but certainly not in the context
> of a packaging system like Guix - that just will breed confusion.
How could better error messages breed confusion?
Also, this seems a change that would absolutely _not_ be considered
upstream. Why would upstream have distro-specific error messages? If
the new error message is Guix-specific, wouldn't Guix be the logical
place to have it?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-03-09 19:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 20:52 [bug#54304] [PATCH] Don't fix git executable location during Elixir build Cees de Groot
2022-03-08 22:16 ` Maxime Devos
2022-03-09 17:35 ` Cees de Groot
2022-03-09 17:59 ` Tobias Geerinckx-Rice via Guix-patches via
2022-03-09 21:01 ` Cees de Groot
2022-03-09 21:49 ` Tobias Geerinckx-Rice via Guix-patches via
2022-03-11 21:33 ` Cees de Groot
2022-03-11 21:51 ` Ludovic Courtès
2022-03-11 21:57 ` Maxime Devos
2022-03-11 22:01 ` Cees de Groot
2022-03-11 22:11 ` Maxime Devos
2022-03-11 22:36 ` Cees de Groot
2022-03-11 22:45 ` Maxime Devos
2022-03-11 22:55 ` Cees de Groot
2022-03-11 23:16 ` Maxime Devos
2022-03-11 23:23 ` Cees de Groot
2022-03-13 22:14 ` Ludovic Courtès
2022-03-13 22:16 ` Cees de Groot
2022-03-08 22:17 ` Maxime Devos
[not found] ` <OtG7oZgFz6vgVWUbmqcU-n34hv-sQCpJYpJKR7rdQvIDnB1sUh_1LoUl9egvv6vKWH_THdYl9gwPrzwzXx_FnxlPXJHaB3D70jY32T3oMuk=@evrl.com>
2022-03-09 7:31 ` Maxime Devos
2022-03-09 17:29 ` Cees de Groot
2022-03-08 22:18 ` Maxime Devos
2022-03-08 22:22 ` Maxime Devos
2022-03-09 17:31 ` Cees de Groot
2022-03-09 19:45 ` Maxime Devos [this message]
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=919b8ca66b9548aa0e3cf682b9e293f7ed28b2a8.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54304@debbugs.gnu.org \
--cc=cg@evrl.com \
/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).