Re: [RFC PATCH] Use script to test build configurations

Todd Zullinger <[email protected]> Sun, 31 May 2026 12:23:24 -0400

Newsgroups	gmane.mail.mutt.devel
Message-ID	<[email protected]>

Hi,

Alejandro Colomar via Mutt-dev wrote:
> Hi Kevin,
> 
> On 2026-05-31T15:57:30+0800, Kevin J. McCarthy wrote:
>> :D.  I don't want to dictate, since you've put the effort in.  My only
>> comment is that "build" sounds like something an ordinary user might try
>> running after checking out the git repos.  So I would vote for moving the
>> script somewhere (under .builds if that is legal), and/or renaming it to
>> something less tempting to run, such as ci-build.
> 
> I would like to avoid hidden dirs.  Could we use something like
> scripts/?

I'm sure plenty of projects have arrived at different paths.
The git project places stuff like this in a top-level 'ci'
directory.

I think something like 'scripts' may be as easily confused
as a top-level 'build' script in the eyes of users who were
not familiar with mutt development.

-- 
Todd

signature.asc (application/pgp-signature, 228 B)