References: <559AE0A8.3080907@morningstar2.co.uk> <55A3E1DD.8050707@posteo.net>
            <55A3E5E6.2060405@morningstar2.co.uk> <55A4137A.7030807@posteo.net>
            <55A415FF.8030305@nag.co.uk> <55A801A8.5090702@posteo.net>
            <55A809C4.70009@nag.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
            Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <55AA1554.3050509@posteo.net>
Date:         Sat, 18 Jul 2015 10:59:00 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Stephan Hennig <sh-list@POSTEO.NET>
Subject: Re: LuaTeX support in the LaTeX kernel
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <55A809C4.70009@nag.co.uk>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

Am 16.07.2015 um 21:45 schrieb David Carlisle:

> There are some differences, and I hope to document them, but may need to
> be during quiet periods at TUG 2015 next week:-) but it would be
> interesting to know of other packages building on luatexbase and whether
> the new code supports them and if not whether the package could easily
> change or if the ltluatex implementation needs to support more features.
> 
> ltluatex is usable with latex and with plain (see the ltluatex.tex file
> for plain support)
> 
> So I do not think there are two API, just a new refactored and extended
> implementation. Certainly the differences are small enough that if a
> small compatibility layer is needed an updated luatexbase.sty could, if
> the luatexbase maintainers agree, input ltluatex and fill any gaps, but
> it may be by the time we are done, there are no gaps that need filling.

OK, so I have these two module loading and callback related feature
requests.  Whom should I contact about those?  LaTeX team or luatexbase
maintainers?

As I understand it, you're trying to make the luatexbase package
obsolete.  Which a) puts additional maintenance burden on the LaTeX team
and b) means that new features related to resource allocation will be
released in sync with new LaTeX versions only (as resource allocation is
completely implemented as part of the format).  I'm still not easy with
this approach.

Best regards,
Stephan Hennig