Documented toolchain for building docs on Windows
Section "17.1. Building with Visual C++ or the Microsoft Windows SDK” in the documentation has a subsection "Building the Documentation” which seems to list a required toolchain which is out of date with information in the Documentation appendix (it still lists OpenJade etc). I don’t know anything about building on Windows so I might be off, but doesn’t that need to be updated to match the new toolchain? cheers ./daniel
Re: Documented toolchain for building docs on Windows
On 6/28/18 12:17, Daniel Gustafsson wrote: > Section "17.1. Building with Visual C++ or the Microsoft Windows SDK” in the > documentation has a subsection "Building the Documentation” which seems to > list > a required toolchain which is out of date with information in the > Documentation > appendix (it still lists OpenJade etc). > > I don’t know anything about building on Windows so I might be off, but doesn’t > that need to be updated to match the new toolchain? Yes, I had complained about this before, but nobody responded. I can review a new text, but I can't write it. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
search.cpan.org is EOL, update links
search.cpan.org has now been EOL’d and turned off, with all URLs redirecting to metacpan.org [1]. While the redirects are likely to the maintained for a long time, we might as well update to avoid the risk of stale redirects. Attached patch changes the few links we have to instead use metacpan. cheers ./daniel [1] https://www.perl.com/article/saying-goodbye-to-search-cpan-org/ search_cpan_eol.patch Description: Binary data
Re: Documented toolchain for building docs on Windows
> On 28 Jun 2018, at 12:39, Peter Eisentraut > wrote: > > On 6/28/18 12:17, Daniel Gustafsson wrote: >> Section "17.1. Building with Visual C++ or the Microsoft Windows SDK” in the >> documentation has a subsection "Building the Documentation” which seems to >> list >> a required toolchain which is out of date with information in the >> Documentation >> appendix (it still lists OpenJade etc). >> >> I don’t know anything about building on Windows so I might be off, but >> doesn’t >> that need to be updated to match the new toolchain? > > Yes, I had complained about this before, but nobody responded. I can > review a new text, but I can't write it. Ah, my archive search skills are apparently lacking, thus the duplicate. Looking at little more at this, the docs mention builddoc.bat which was replaced in 2011 in favor of builddoc.pl. This program in turn is using openjade and is thus, I assume, not working anymore. 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”? cheers ./daniel
Re: Add Pgfe library to client interfaces
On Fri, Jun 1, 2018 at 05:56:34PM +0300, Dmitry Igrishin wrote: > Hello, > > Could we please add Pgfe client library to the external interfaces section? > > Patch is attached. Is everyone good with adding this? Is it too new? Also libpqxx is listed in our docs as "New-style C++ interface". Should we remove the "New" part? --- > diff --git a/doc/src/sgml/external-projects.sgml > b/doc/src/sgml/external-projects.sgml > index 347b830..c74e391 100644 > --- a/doc/src/sgml/external-projects.sgml > +++ b/doc/src/sgml/external-projects.sgml > @@ -83,6 +83,13 @@ > > > > + Pgfe > + C++ > + An API inspired by libpq > + https://github.com/dmitigr/pgfe";> > + > + > + >node-postgres >JavaScript >Node.js driver -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
Re: Add Pgfe library to client interfaces
> On 28 Jun 2018, at 15:32, Bruce Momjian wrote: > > On Fri, Jun 1, 2018 at 05:56:34PM +0300, Dmitry Igrishin wrote: >> Hello, >> >> Could we please add Pgfe client library to the external interfaces section? >> >> Patch is attached. > > Is everyone good with adding this? Is it too new? Since the linked repository readme states "ATTENTION, this software is "beta" quality", does it makes more sense to just list it on the wiki for now (which it already is on the Client_Libraries page). cheers ./daniel
Re: Add Pgfe library to client interfaces
On Thu, Jun 28, 2018 at 04:03:36PM +0200, Daniel Gustafsson wrote: > > On 28 Jun 2018, at 15:32, Bruce Momjian wrote: > > > > On Fri, Jun 1, 2018 at 05:56:34PM +0300, Dmitry Igrishin wrote: > >> Hello, > >> > >> Could we please add Pgfe client library to the external interfaces section? > >> > >> Patch is attached. > > > > Is everyone good with adding this? Is it too new? > > Since the linked repository readme states "ATTENTION, this software is "beta" > quality", does it makes more sense to just list it on the wiki for now (which > it already is on the Client_Libraries page). Oh, seems perfect. Thanks. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
Re: Add Pgfe library to client interfaces
> On Jun 28, 2018, at 7:03 AM, Daniel Gustafsson wrote: > >> On 28 Jun 2018, at 15:32, Bruce Momjian wrote: >> >> On Fri, Jun 1, 2018 at 05:56:34PM +0300, Dmitry Igrishin wrote: >>> Hello, >>> >>> Could we please add Pgfe client library to the external interfaces section? >>> >>> Patch is attached. >> >> Is everyone good with adding this? Is it too new? > > Since the linked repository readme states "ATTENTION, this software is "beta" > quality", does it makes more sense to just list it on the wiki for now (which > it already is on the Client_Libraries page). Probably. There are interfaces I know have been in widespread use for a decade or more that aren't listed in the manual, so adding a WIP might not be the most appropriate thing. Finishing up that wiki page (I think Go is the main thing I didn't get around to adding yet) and linking to it from somewhere obvious is probably a good idea, though. Cheers, Steve
Re: Add Pgfe library to client interfaces
чт, 28 июн. 2018 г. в 17:03, Daniel Gustafsson : > > On 28 Jun 2018, at 15:32, Bruce Momjian wrote: > > > > On Fri, Jun 1, 2018 at 05:56:34PM +0300, Dmitry Igrishin wrote: > >> Hello, > >> > >> Could we please add Pgfe client library to the external interfaces > section? > >> > >> Patch is attached. > > > > Is everyone good with adding this? Is it too new? > > Since the linked repository readme states "ATTENTION, this software is > "beta" > quality", does it makes more sense to just list it on the wiki for now > (which > it already is on the Client_Libraries page). > You are right. On the other hand, "H.1. Client Interfaces" refers to the external projects. I.e., by definition, PGDG is *not* responsible for the quality of these projects. I honestly noted that my library is on "beta" stage, and this is *my* subjective opinion. Does this mean specifically that this project can not be mentioned in the documentation? I *my* subjective opinion - no. Therefore, if someone refers to my opinion about the "beta", then why should he not refer to my opinion regarding the mention of my library in the official documentation? It seems to *me* logical. But, please note. I don't insist on my proposal. I just think I did some thing for PostgreSQL, which is worthy of mention in the PostgreSQL documentation. That's all. PS. I glad that my library is mentioned in the wiki. Thank you all!
Re: search.cpan.org is EOL, update links
On Thu, Jun 28, 2018 at 01:00:47PM +0200, Daniel Gustafsson wrote: > search.cpan.org has now been EOL’d and turned off, with all URLs redirecting > to > metacpan.org [1]. While the redirects are likely to the maintained for a long > time, we might as well update to avoid the risk of stale redirects. Attached > patch changes the few links we have to instead use metacpan. Okay, let's fix that. While working on the links for CPAN, perhaps these should be switched to https as well? src/sgml/acronyms.sgml: http://www.cpan.org/";>Comprehensive Perl Archive Network contrib/fuzzystrmatch/dmetaphone.c: version 0.05 available from http://www.cpan.org. -- Michael signature.asc Description: PGP signature
Re: search.cpan.org is EOL, update links
> On 29 Jun 2018, at 03:23, Michael Paquier wrote: > > On Thu, Jun 28, 2018 at 01:00:47PM +0200, Daniel Gustafsson wrote: >> search.cpan.org has now been EOL’d and turned off, with all URLs redirecting >> to >> metacpan.org [1]. While the redirects are likely to the maintained for a >> long >> time, we might as well update to avoid the risk of stale redirects. Attached >> patch changes the few links we have to instead use metacpan. > > Okay, let's fix that. > > While working on the links for CPAN, perhaps these should be switched to > https as well? Good point, we might as well do that too. Fixed those two and an additional one in the attached updated version. cheers ./daniel search_cpan_eol-v2.patch Description: Binary data
