Richard Heck wrote: > Ick. OK, then, we can do that. I'm still not sure this is enough. I recall having seen (and even introduced) uses of requires where the output is done at a completely different place. The require("CJK") call in LaTeXFeatures::useLanguage is such a case. This still would fall through with your extended list.
Basically, I think we need to introduce a method to "register" something as a package before we require it. Jürgen