From: Maxime Devos <maximedevos@telenet.be>
To: Timothy Sample <samplet@ngyro.com>
Cc: guile-devel@gnu.org
Subject: Re: automake test driver for Guile scheme patch review
Date: Wed, 22 Nov 2023 00:08:07 +0100 [thread overview]
Message-ID: <d9d51204-cc65-21cb-be68-30b480418711@telenet.be> (raw)
In-Reply-To: <8734wy3e35.fsf@ngyro.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1483 bytes --]
Op 22-11-2023 om 00:02 schreef Timothy Sample:
> Hello,
>
> [Dropping Karl since we are no longer discussing Automake maintenance.]
>
> Maxime Devos <maximedevos@telenet.be> writes:
>
>> [What about] discoverability, ease of updating the test driver,
>> clarity, unbundling and the goals of Freja Nordsiek?
>
> Maybe Guile should adopt the script as ‘guild test-am’ or somesuch.
While written for Automake, it's useful and usable outside it, so I
would change 'am' to something else. Maybe: ‘guild run-test-suite’.
> Mathieu assigned copyright to the FSF for the Automake patch and I
> believe Maxim would be willing to do the same for the more recent
> patches.
Note: while accepted, that's not a requirement anymore.
> If there’s interest and someone willing to commit the change, I
> volunteer to integrate the script. I can add a node in the manual after
> “4.8 Distributing Guile Code” called “Testing Guile Code” that links to
> Maxim’s forthcoming SRFI 64 documentation and explains how to use the
> script with Automake.
>
> Thoughts?
I don't know if there is someone willing to commit the change (as in, I
don't know, not I know there isn't someone willing), but I would say
there is definitely interest.
(Doesn't matter for me whether it's in Guile or a thing packaged
separately ... just not this script that gets copied around with
somewhat unclear providence.)
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-21 23:08 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
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 [this message]
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=d9d51204-cc65-21cb-be68-30b480418711@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=samplet@ngyro.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.
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).