Re: [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)
On 2/3/14, 8:48 PM, Tom Lane wrote: That's a very fair question. It's a reasonable bet that pretty much nobody actually looks at the text versions of either HISTORY or regress_README anymore. It's conceivable that somebody somewhere makes use of the text version of INSTALL when trying to get PG going on some bare-bones platform ... but really, can't they look it up on the net? How'd they get the PG sources they're installing, anyway? I think having an INSTALL file is good form, and it costs us little to maintain it. The other files could be removed, IMO. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)
Peter Eisentraut pete...@gmx.net writes: On 2/3/14, 8:48 PM, Tom Lane wrote: That's a very fair question. It's a reasonable bet that pretty much nobody actually looks at the text versions of either HISTORY or regress_README anymore. It's conceivable that somebody somewhere makes use of the text version of INSTALL when trying to get PG going on some bare-bones platform ... but really, can't they look it up on the net? How'd they get the PG sources they're installing, anyway? I think having an INSTALL file is good form, and it costs us little to maintain it. The other files could be removed, IMO. That seems like a reasonable compromise to me. The HISTORY file is certainly the worst pain-in-the-rear among these, since it's generated from files that we change constantly, and so we're always tripping over the link restrictions. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)
On 08/02/14 19:05, Tom Lane wrote: Peter Eisentraut pete...@gmx.net writes: On 2/3/14, 8:48 PM, Tom Lane wrote: That's a very fair question. It's a reasonable bet that pretty much nobody actually looks at the text versions of either HISTORY or regress_README anymore. It's conceivable that somebody somewhere makes use of the text version of INSTALL when trying to get PG going on some bare-bones platform ... but really, can't they look it up on the net? How'd they get the PG sources they're installing, anyway? I think having an INSTALL file is good form, and it costs us little to maintain it. The other files could be removed, IMO. That seems like a reasonable compromise to me. The HISTORY file is certainly the worst pain-in-the-rear among these, since it's generated from files that we change constantly, and so we're always tripping over the link restrictions. regards, tom lane How about adding URL's for the online versions of HISTORY README's (or their rough equivalents - perhaps the online version of the latest 'Appendix E. Release Notes' would be sufficient?) to the INSTALL file? Cheers, Gavin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)
Gavin Flower gavinflo...@archidevsys.co.nz writes: How about adding URL's for the online versions of HISTORY README's (or their rough equivalents - perhaps the online version of the latest 'Appendix E. Release Notes' would be sufficient?) to the INSTALL file? Actually, what I had in mind was to replace the dynamically-generated HISTORY and README files with small text files that contain those URL references. If we remove those files from the distribution tarballs altogether, it'd likely break some packagers' recipes (I know for sure it'd break the Red Hat RPM specs, for instance). But packaging should still work if they're there but smaller. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)
Noah Misch n...@leadboat.com writes: Robert Haas robertmh...@gmail.com writes: I wonder if these standalone things are really worthwhile. I wonder how difficult it would be to make sufficient link data available when building the standalone files. There would be no linking per se; we would just need the referent's text fragment emitted where the xref tag appears. IIRC, that's basically what the workaround is, except it's not very automated. Even if it were automated, though, there's still a problem: such links aren't really *useful* in flat text format. I think that forcing the author to actually think about what to put there in the flat text version is a good thing, if we're going to retain the flat text version at all. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
