unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Timothy Sample <samplet@ngyro.com>
Cc: Karl Berry <karl@freefriends.org>, guile-devel@gnu.org
Subject: Re: automake test driver for Guile scheme patch review
Date: Tue, 21 Nov 2023 18:33:40 +0100	[thread overview]
Message-ID: <a69187f3-1c7e-8e32-1d82-278763fe9d41@telenet.be> (raw)
In-Reply-To: <87msv82ye9.fsf@ngyro.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2256 bytes --]



Op 20-11-2023 om 17:16 schreef Timothy Sample:
> Hi,
> 
> Maxime Devos <maximedevos@telenet.be> writes:
> 
>> 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.
>>
>> 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.
> 
> Well, it’s already a part of Automake as ‘contrib/test-driver.scm’:
> 
> https://git.savannah.gnu.org/cgit/automake.git/tree/contrib/test-driver.scm

Last time I tried, "autoreconf -i" doesn't pick it up, so apparently 
it's not part of Automake in any way that matters, it's only part of the 
Automake repository. (Also, it's undocumented.)

Besides, if it were added to Automake at one point, it can be removed 
from Automake (and added somwhere else) at another.

>> Also, the test driver has been updated since then.
> 
> That’s true.  Maxim Cournoyer added some useful features in 2021.
> However, these features do not affect Automake.  They only make the
> script more useful when running outside of Automake.  It would be nice
> to have them in the Automake version, but I guess Maxim would have to
> sign a copyright assignment for that.  (I’m not sure of Automake’s
> policy there, so correct me if I’m wrong.)

Looking at the commit messages, they are useful within Automake as well
do in fact, affect Automake.  For example, one of these changes is a new 
"--show-duration" option, which can be used within Automake by:

$ make check SCM_LOG_DRIVER_FLAGS="--brief=no --show-duration=yes"

(copied from doc/guix.texi).

> I think that doing nothing other than closing that patch would be a
> reasonable course of action.  :)

And how is "doing nothing" supposed to help with discoverability, ease 
of updating the test driver, clarity, unbundling and the goals of Freja 
Nordsiek?

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 --]

  reply	other threads:[~2023-11-21 17:33 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 [this message]
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=a69187f3-1c7e-8e32-1d82-278763fe9d41@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guile-devel@gnu.org \
    --cc=karl@freefriends.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).