On 5/6/14 10:20 PM, Peter Eisentraut wrote:
Agreed. I have committed the SGML changes that make things valid now,
but I will postpone the xmllint addition until the 9.5 branch, complete
with more documentation.
Per the above announcement, here is an updated patch, also with more
documentation
Peter Eisentraut pete...@gmx.net writes:
It would especially be valuable if someone with a different-than-mine OS
would verify whether they can install xmllint according to the
documentation, or update the documentation if not.
FWIW, xmllint appears to be part of the base libxml2 package on
On Thu, 2014-05-01 at 22:51 -0400, Tom Lane wrote:
But we don't have xmllint installed on borka, where we build the
releases. Could someone please install it?
-1. Doesn't this break make man for *any* hacker who doesn't have
xmllint installed?
Please change the patch so that it runs
Peter Eisentraut pete...@gmx.net writes:
On Thu, 2014-05-01 at 22:51 -0400, Tom Lane wrote:
-1. Doesn't this break make man for *any* hacker who doesn't have
xmllint installed?
The intention is that we enforce that the documentation is correctly
formatted. Enforcing that only when the
Tom Lane wrote:
(The subtext here is that borka is absolutely not an acceptable place
to encounter documentation build failures. By the time we're at that
stage of the release cycle, I don't really care what xmllint might
have to say; there isn't going to be time to make it happy.)
Borka is
Peter Eisentraut wrote:
I have been working on making the DocBook XML output valid. The first
part was bb4eefe7bf518e42c73797ea37b033a5d8a8e70a, I now have the rest
ready, but I'll spare you the mostly mechanical 200kB patch for now. In
addition, I'd like to add the attached patch with an
I have been working on making the DocBook XML output valid. The first
part was bb4eefe7bf518e42c73797ea37b033a5d8a8e70a, I now have the rest
ready, but I'll spare you the mostly mechanical 200kB patch for now. In
addition, I'd like to add the attached patch with an xmllint call to
make sure
Peter Eisentraut pete...@gmx.net writes:
I have been working on making the DocBook XML output valid. The first
part was bb4eefe7bf518e42c73797ea37b033a5d8a8e70a, I now have the rest
ready, but I'll spare you the mostly mechanical 200kB patch for now. In
addition, I'd like to add the attached
