Re: split func.sgml to separated individual sgml files

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: split func.sgml to separated individual sgml files
Дата
Msg-id 1a609094-4baf-4980-be90-1b3232b35bb2@eisentraut.org
обсуждение исходный текст
Ответ на Re: split func.sgml to separated individual sgml files  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: split func.sgml to separated individual sgml files
Список pgsql-hackers
On 01.10.25 22:02, Andrew Dunstan wrote:
> 
(Maybe these discussions could have been in a new thread and not hidden 
under some unrelated thing.)
> OK, thanks, looks good. How do we go about doing what Tom wants (i.e. 
> running the tests by default) under meson. I think in the Makefile we 
> could just add it to the html target.

-html: html-stamp
+html: check html-stamp

This is not a good solution.  This means the html target is never up to 
date.  Compare PostgreSQL 18:

$ make html
make: Nothing to be done for 'html'.
$ make -q html; echo $?
0

And master:

$ make html
perl ...
$ make -q html; echo $?
1

Also, consider the postgres-full.xml target:

# Run validation only once, common to all subsequent targets.  While
# we're at it, also resolve all entities (that is, copy all included
# files into one big file).  This helps tools that don't understand
# vpath builds (such as dbtoepub).
postgres-full.xml: postgres.sgml $(ALL_SGML)
     $(XMLLINT) $(XMLINCLUDE) --output $@ --noent --valid $<

Note that this already does validation.  The way this is structured now 
is that it runs the validation once when you create postgres-full.xml, 
which is than later input into the HTML generation, and then you run the 
validation again, on the already-processed input files, which doesn't 
make any sense.

I suspect what you're really after here is the functionality of the 
check-tabs and check-nbsp targets.  So the new Perl script really just 
has to cover those two and doesn't have to bother with xmllint.  And 
then you just call that script as part of the postgres-full.xml target.




В списке pgsql-hackers по дате отправления: