On Wed, Sep 5, 2012 at 09:56:32PM -0300, Alvaro Herrera wrote:
> Excerpts from Tom Lane's message of mié sep 05 20:24:08 -0300 2012:
> > Andrew Dunstan <andrew@dunslane.net> writes:
> > > The only reason there is a significant delay is that the administrators
> > > have chosen not to run the process more than once every 4 hours. That's
> > > a choice not dictated by the process they are using, but by other
> > > considerations concerning the machine it's being run on. Since I am not
> > > one of the admins and don't really want to take responsibility for it I
> > > am not going to second guess them. On the very rare occasions when I
> > > absolutely have to have the totally up to date docs I build them myself
> > > - it takes about 60 seconds on my modest hardware.
> >
> > I think the argument for having a quick docs build service is not about
> > the time needed, but the need to have all the appropriate tools
> > installed. While I can understand that argument for J Random Hacker,
> > I'm mystified why Bruce doesn't seem to have bothered to get a working
> > SGML toolset installed. It's not like editing the docs is a one-shot
> > task for him.
>
> As far as I understand, Bruce's concern is not about seeing the docs
> built himself, but having an HTML copy published somewhere that he can
> point people to, after applying some patch. To me, that's a perfectly
> legitimate reason to want to have them quickly.
Correct. I have always had a working SGML toolset. If we are not going
to have the developer site run more often, I will just go back to
setting up my own public doc build, like I used to do. I removed mine
when the official one was more current/reliable --- if that has changed,
I will return to my old setup, and publish my own URL for users to
verify doc changes.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +
