Re: remove dead ports? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: remove dead ports?
Date
Msg-id 20120505164414.GA4273@momjian.us
Whole thread Raw
In response to Re: remove dead ports?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: remove dead ports?
List pgsql-hackers
On Sat, May 05, 2012 at 12:08:00PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Sat, May 05, 2012 at 11:26:32AM -0400, Tom Lane wrote:
> >> Possibly.  What exactly is the difference between the "sco" and
> >> "unixware" ports, anyway?  The one buildfarm member we have running
> >> SCO software (koi) chooses the unixware template.
> 
> > Unixware was based on Unix System Labs System V, Release 4, while SCO
> > was based on a 286 port of SVr2, or something like that.
> 
> Oh, so the "sco" port actually refers to OpenServer?
> 
>     http://en.wikipedia.org/wiki/SCO_OpenServer
> 
> That page makes it sound like it's more or less as current as Unixware,
> since both had their last updates in 2008/2009 timeframe (and both
> are presumably never going to see another one, with SCO the company
> being dead in all but name).
> 
> The difference from our perspective is that we have a buildfarm member
> running Unixware, whereas it's anybody's guess whether the "sco" port
> still works or not.

Well, absent user feedback, we could use our own 5-year rule and keep
sco and unixware, and remove irix (2006).

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: smart shutdown at end of transaction (was: Default mode for shutdown)
Next
From: Jan Urbański
Date:
Subject: Re: PL/Python result set slicing broken in Python 3