On Mon, Jun 11, 2018 at 11:36:48PM +0200, Daniel Gustafsson wrote:
> > On 11 Jun 2018, at 23:24, Bruce Momjian <bruce@momjian.us> wrote:
> >
> > On Sun, Jun 10, 2018 at 09:29:51PM +0200, Daniel Gustafsson wrote:
> >>> On 10 Jun 2018, at 04:16, Bruce Momjian <bruce@momjian.us> wrote:
> >>>
> >>> Would someone please apply this patch to the website code so pglife
> >>> (http://pglife.momjian.us/) can more easily scrape the current release
> >>> numbers from the website? Thanks.
> >>
> >> While harmless enough, I’m not a huge fan of adding identifiers to the site
> >> which are not in use in the site code, such non-obvious external dependencies
> >> make the code harder to maintain.
> >>
> >> If you are using XPath expressions to access the values, would something like
> >> this on the versioning page suffice for what you’re after?
> >>
> >> //*[@id="pgContentWrap"]/table/tbody/tr/td[text()="Yes"]/../td[2]
> >
> > What is the URL of the versioning page? This one?
> >
> > https://www.postgresql.org/about/featurematrix/
>
> I was looking at the Versioning Policy page under Support:
>
> https://www.postgresql.org/support/versioning/
Oh, yes, that would work, except I like links to the release notes which
are on the main page. I ended up just adding a loop over the DIVs
looking for H2 text "Latest Releases" and it worked just fine. Pglife
is now fixed. Thanks.
--
Bruce Momjian <bruce@momjian.us> 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 +