| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: documentation structure |
| Date: | 2024-03-22 15:50:21 |
| Message-ID: | CAKFQuwa0B0Levwh=iEgW+p33RL6zhSJ+_YazpQD9qhW6Vu_AVg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 22, 2024 at 7:10 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> That's actually what we had in chapter
> 18, "Installation from Source Code on Windows", since removed. But for
> some reason we decided that on non-Windows platforms, it needed a
> whole new chapter rather than an extra sentence in the existing one. I
> think that's massively overkill.
>
>
I agree with the premise that we should have a single chapter, in the main
documentation flow, named "Installation". It should cover the
architectural overview and point people to where they can find the stuff
they need to install PostgreSQL in the various ways available to them. I
agree with moving the source installation material to the appendix. None
of the sections under Installation would then actually detail how to
install the software since that isn't something the project itself handles
but has delegated to packagers for the vast majority of cases and the
source install details are in the appendix for the one "supported"
mechanism that most people do not use.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-03-22 15:51:00 | Re: [PATCH] plpython function causes server panic |
| Previous Message | Viliam Ďurina | 2024-03-22 15:50:01 | Re: MIN/MAX functions for a record |