Re: have TEXINFO_XS=required adapted to TEXINFO_XS_*=0 and disabled XS

On Fri, Jan 23, 2026 at 06:39:50PM +0000, Gavin Smith wrote:
> On Fri, Jan 23, 2026 at 12:48:38AM +0100, Patrice Dumas wrote:
> > What I would like to add is the possibility to set TEXINFO_XS to some
> > value that leads to a failure if some XS modules that could be loaded
> > given the values of TEXINFO_XS_* are not loaded.  TEXINFO_XS=required as
> > it is now cannot play that role, because if a XS modules is not loaded
> > because it is implied by the TEXINFO_XS_* value the command fails.
> 
> That all sounds fine but I would like to keep "required" as it is.  It's
> fine to add another option.  I suggest "requiredifenabled".  The "enabled"
> part could refer to the result of running 'configure' or the TEXINFO_XS_*
> variables.

Ok, I'll use that.

> I've got in mind to think about how to report status of XS code better
> for the test suite, but haven't been able to get to this yet.

My current idea with the requiredifenabled possibility is to use it such
that there is no need to report anything, if the state is no exactly the
expected state, there would be a failure.

-- 
Pat