From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Documented toolchain for building docs on Windows
Date: Fri, 13 Jul 2018 10:09:00 +0200
Message-ID: <e4d95bd9-5c1d-0b85-02d9-e01377a7299e@2ndquadrant.com> (raw)
In-Reply-To: <DD4B0A0C-BA20-4258-92AF-140009518C92@yesql.se>
References: <B74C0219-6BA9-46E1-A524-5B9E8CD3BDB3@yesql.se>
<d78ca400-86c3-f971-3c26-3e194e0b859c@2ndquadrant.com>
<4EC74690-CBD5-4C42-BEA3-30C85ECD904E@yesql.se>
<e0d18f36-b262-7a63-6eb2-3d3a3ecbbd27@2ndquadrant.com>
<DD4B0A0C-BA20-4258-92AF-140009518C92@yesql.se>
On 29.06.18 18:51, Daniel Gustafsson wrote:
>> On 29 Jun 2018, at 15:08, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
>>
>> On 6/28/18 13:19, Daniel Gustafsson wrote:
>>> Unless someone steps up before 11 is rolled, maybe builddoc.pl should be made
>>> into a exit immediately no-op since "nothing" is better than “broken”?
>>
>> I'm thinking, just delete the file and the documentation section.
>
> Well, that's a pretty decisive way to make it a no-op =) The attached patch
> does that, along with a note in the relnotes to highlight the dropped support
> which I think is warranted should we take this approach.
I have committed this to master now. The scripts have already been
broken since PG10, so mentioning it in the PG11 release notes doesn't
seem appropriate.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, daniel@yesql.se
Subject: Re: Documented toolchain for building docs on Windows
In-Reply-To: <e4d95bd9-5c1d-0b85-02d9-e01377a7299e@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox