User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0)
            Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
References: <LATEX-L%201208101400309140.36EB@LISTSERV.UNI-HEIDELBERG.DE>       
            <502502DA.7050009@gmail.com>
            <CANQYN6y9eA9YqVg+MoYoG4fWp4VPAY3rFhRJNz1WQKvwhh3thQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <502583F5.5000805@morningstar2.co.uk>
Date:         Fri, 10 Aug 2012 22:58:13 +0100
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: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Examples of l3doc & unit testing?
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <CANQYN6y9eA9YqVg+MoYoG4fWp4VPAY3rFhRJNz1WQKvwhh3thQ@mail.gmail.com>
Precedence: list
Status: R

On 10/08/2012 19:29, Bruno Le Floch wrote:
> One of my main concerns, after looking at the plethora of Makefiles
> and make.bat is that there is a lot of redundancy there, which means
> that (1) changes don't propagate well (2) we occasionally forget to
> add a module to the Makefile of the parent directory, and it never
> gets tested, installed, unless someone is working on that module.
>
> So I guess that in the LaTeX3 case the discussion should be extended
> to the build system as a whole: the test system works well, as Frank
> says.  It would be nice if we could get rid of Makefiles and make.bat,
> and replace them by light-weight configuration files.  After all, the
> Makefiles are all very similar, so a top-level Lua script (or other)
> should be able to do most of the work.

I did consider working to have fewer files, but the problem seemed to be
that each module should be usable independently (install/test/document),
so you need some form of stub in each directory. Once you do that, it
seems somewhat pointless to go to the effort of passing all the
requirements as arguments or similar. It's also the case that l3kernel
has different requirements from everything else.

Over all, there is a question of time balance. We have a lot to do on
the TeX side, and also should be aiming to move 'experimental' material
to a more 'usable' state. Thus the long-term target is for
l3kernel/l3packages to contain most (all?) of the code, which means
fewer build scripts for the most important material. So when I last
looked at the build system it did not seem like a good use of my time to
spend it rejigging a system which already works and which does not
itself add code to LaTeX3.

> The guy might have an old TeX distro :).  Probably you're right that
> all potential LaTeX3 testers probably have a reasonably up-to-date
> distro.  However, how "up-to-date" does it have to be?  Anyone knows
> when texlua was introduced?

Certainly after pdfTeX 1.30.0, which is the base requirement to run
LaTeX3 code ;-)
-- 
Joseph Wright