Re: remove dead ports?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: remove dead ports?
Date: 2012-05-05 08:59:54
Message-ID: 1336208394.13755.4.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On fre, 2012-05-04 at 18:25 -0400, Tom Lane wrote:
> What's the grounds for asserting they were known not to work? Not
> actual testing, I assume.

There were either essential pieces missing (e.g., no shared library
support, or no Makefile.port), or we had received reports in the past
the platform doesn't work and won't be fixed anymore by the original
supporter.

> Furthermore, I would want to insist that a complainer provide a
> buildfarm member as the price of us continuing to support an old
> uncommon platform. Otherwise the apparent support is hollow. The BSDI
> port was viable for us to support as long as Bruce was using it daily,
> but with that gone, we need somebody else to be testing it.

Based on these emerging criteria, should we also remove the other
platforms on my original "marginal" list?

irix
osf
sco

irix and osf support was already dropped in Python 3.0, so probably
their time is up.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2012-05-05 09:06:15 Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ?
Previous Message Peter Eisentraut 2012-05-05 08:49:10 Re: remove dead ports?