Joseph Wright

Note that the biggest single issue is that LuaTeX normalisation depends on the release. So you have to update `.tlg` files every TeX Live release. That doesn't mean that `l3build`...

I think with the move to a stand-alone script it will make sense to say that we only support the latest releases _once_ TL'18 is out (and so the script...

I think we are now in a position where it's 'any recent release' - I'd expect TL'20 and TL'21 to work at least.

I think that will work but I wonder if we should instead change the docs: @zauguin thoughts?

Fixed by altering docs

Er, no one should have files with `*` or `?` in the name: I'm not sure it's even possible! (`cmd.exe` would I suspect just give up.)

> on unix > > ``` > touch "a?b*c.text" > ``` > > is legal... Sure but not on Windows, and we are looking at a cross-platform tool.

Is this still relevant at the `l3build` end?

The MakeIndex files had to be special-cased as we can't install for both `master` and `develop`. I'll check where I did that and why we then don't get a clean...

I was thinking we'd want generic switches, so some form of 'do/do not disable INFO'. Would that work? Probably would be ```latex \def\DONOTSETPDFINFO{} \input regression-test % ``` where we simply...