Re: split func.sgml to separated individual sgml files
От | Nazir Bilal Yavuz |
---|---|
Тема | Re: split func.sgml to separated individual sgml files |
Дата | |
Msg-id | CAN55FZ2bxpeR2Y91ymJv5RsM6LFvKqN5U933cMDjk+VTvYoACA@mail.gmail.com обсуждение исходный текст |
Ответ на | 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 |
Hi, On Fri, 3 Oct 2025 at 18:47, Andrew Dunstan <andrew@dunslane.net> wrote: > > On 2025-10-03 Fr 10:41 AM, Tom Lane wrote: > > Peter Eisentraut <peter@eisentraut.org> writes: > > If you look at this more closely, creating postgres-full.xml and running > the syntax check perform the same operations, except that the latter > throws away the output. So it seems redundant to build a whole new code > path for this. I think you can make the check target dependent on > postgres-full.xml and be done, kind of like this (starting from > pre-b2922562726): > > Would it be unreasonable to discard the "check" target altogether? > It made sense back in the day when actually building the html docs > took many minutes. But I haven't used it in years, so I wonder > if anyone else has either. > > I have no objection. We'll need to work out what we're doing on the meson side, which is kinda where we came in ... I can work on this but I want to clarify it first. Which one do you prefer: 1- We won't have any command to do syntax checks (including tab and nbsp), these checks will automatically run when we generate docs. 2- We will have a 'check' target but it will only do tab and nbsp checks; xmllint will run only when generating the docs. -- Regards, Nazir Bilal Yavuz Microsoft
В списке pgsql-hackers по дате отправления: