Add switch -s|--stdengine

[josephwright]

No description provided.

[muzimuzhi]

Need to be added to the big list of options

l3build/l3build.dtx

Lines 369 to 372 in 3d51aae

	% As well as these targets, the system recognises the options
	% \begin{itemize}
	% \item |--config| (|-c|) Configuration(s) to use for testing
	% \item |--date| Date to use when tagging data

Also searching for -s in l3build.pdf I spot an existing typo mentioning -s (lowercase s) (on line 460, see below), which was introduced in c4471ca (Add new --rerun|-r option (#17), 2017-07-01) hence looks like it should be -r (short for --rerun).

l3build/l3build.dtx

Lines 454 to 461 in 3d51aae

	% \begin{buildcmd}{check \meta{name(s)}}
	% Checks only the test \texttt{\meta{name(s)}.lvt}.
	% All engines specified by \var{checkengines} are tested unless the command
	% line option |--engine| (or |-e|) has been given to limit
	% testing to a single engine. Normally testing is preceded by unpacking
	% source files and copying the result plus any additional support to the
	% test directory: this may be skipped using the |-s| option.
	% \end{buildcmd}

Update: Addressed in f0d095b (Correct rerun docs, 2024-01-17).

[FrankMittelbach]

somebody remarked that this should be also in the main (pdf) documentation. Otherwise, looks fine. (somebody was Yukai, as I now see :-))

[FrankMittelbach]

not really for this pr but seeing this line: shouldn't in case of -e the checkengines variable set to the \cap of "engine" and the existing "checkengines" of a config file?

[josephwright]

Not necessarily - you can add -f for force running with an 'unsuitable' engine

[josephwright]

-- Sanity check
function check_engines(config)
  if options["engine"] and not options["force"] then
    -- Make a lookup table
    local t = { }
    for _, engine in pairs(checkengines) do
      t[engine] = true
    end
    for _, engine in pairs(options["engine"]) do
      if not t[engine] then
        print("\n! Error: Engine \"" .. engine .. "\" not set up for testing with configuration \"" .. config .. "\"!")
        print("\n  Valid values are:")
        for _, engine in ipairs(checkengines) do
          print("  - " .. engine)
        end
        print("")
        exit(1)
      end
    end
  end
end

[FrankMittelbach]

I nevery really understood the use case for force :-) but yes, that makes it a little more complicated. But in case of asking for -ewithout -f: wouldn't it be more oportune to simply not do any tests for any of the "e" engines that are not in "checkengines" of a particular config rather calling it an error? Well maybe not, dunno

[josephwright]

Well we could drop --force: it was there for some setup stuff which likely we no longer need (and I think -s makes redundant).

[josephwright]

That could be done separate from the PR of course

[FrankMittelbach]

we could I guess, and yes it should be done in a separate pr.