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

"Kevin J. McCarthy" <[email protected]> Sun, 31 May 2026 15:57:30 +0800

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

On Sun, May 31, 2026 at 07:57:43AM +0200, Rene Kita wrote:
>I implemented this for w3m a few days ago and was wondering if this
>might be of interest for mutt. The idea is that all build configurations
>live in a shell script rather then being split over multiple build
>manifests. This allows to test all configurations locally by just
>calling the script. It also avoid having to write the same config over
>and over again for every manifest.

This sounds reasonable.

>Note that this currently breaks the CI as I found out, that the
>'original' task was different depending on the image we were building
>on. E.g. on Alpine we use --with-sasl while on OpenBSD we used
>--without-sasl.

Is this something you need help resolving? i.e., Do we just need to
update the required packages, or is there a bug to resolve?

>Please bikeshed the script name 'build' and if it should be placed in
>the root directory. I kept the name from w3m, but there it is placed
>in the test directory which makes it more obvious what the intend is.

: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.

>If there is interest I will continue to fix the build problems and unify
>the build configurations.

Absolutely, from my point of view.  I appreciate your work on this!

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

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