From: Maxime Devos <maximedevos@telenet.be>
To: Karl Berry <karl@freefriends.org>, guile-devel@gnu.org
Subject: Re: automake test driver for Guile scheme patch review
Date: Mon, 20 Nov 2023 00:43:12 +0100 [thread overview]
Message-ID: <460c1ea1-443e-2daf-ebb6-185bc5aff161@telenet.be> (raw)
In-Reply-To: <202311191717.3AJHHSmf002423@freefriends.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1706 bytes --]
Op 19-11-2023 om 18:17 schreef Karl Berry:
> Hello Guile folk - back in May 2016, Mathieu Lirzin submitted a patch to
> add a test driver for Guile Scheme to Automake.
> https://lists.gnu.org/archive/html/automake-patches/2016-05/msg00000.html
>
> It was never committed. It's been seven+ years, so before doing so, I
> wanted to check if it was still useful, and valid. I know next to
> nothing about Guile or Guix myself.
>
> Please advise? If this is the wrong list, please forward? --thanks, karl.
>
> (I'm not on this list, so please cc me with any replies.)
>
Useful, but I don't think it should be in Automake, because then the
test driver is harder to update and it would add yet another source of
bundling. Instead, I think the test driver should be a separate
package/program (with support in Automake for invoking the driver) or
part of Guile (maybe a "guild test" subcommand or something like that).
I don't have any advise on how to get the automake maintainers to
actually respond to the patch beyond ‘maybe try again?’.
Also, the test driver has been updated since then. As far as I can
tell, Guix is currently the upstream of the test driver (see:
build-aux/test-driver.scm) -- while part of Guix, it should be
straightforward enough to only install the test driver itself in
distributions, without compiling or installing the rest of Guix.
(See, e.g. https://issues.guix.gnu.org/58365#9, where test-driver.scm
(from Guix) is packaged as a Guix package, albeit not the best example
because both are Guix.)
If you retry merging it into Automake, I recommend picking up the new
version from Guix.
Best regards,
Maxime Devos
[-- 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:[~2023-11-19 23:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 17:17 automake test driver for Guile scheme patch review Karl Berry
2023-11-19 19:55 ` Freja Nordsiek
2023-11-19 23:43 ` Maxime Devos [this message]
2023-11-20 16:16 ` Timothy Sample
2023-11-21 17:33 ` Maxime Devos
2023-11-21 22:57 ` Maxime Devos
2023-11-21 23:02 ` Timothy Sample
2023-11-21 23:08 ` Maxime Devos
2023-11-23 4:19 ` Maxim Cournoyer
2023-11-21 21:45 ` Karl Berry
2023-11-22 20:05 ` Freja Nordsiek
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=460c1ea1-443e-2daf-ebb6-185bc5aff161@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=karl@freefriends.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 read-only IMAP folder(s) and NNTP newsgroup(s).