From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: remove dead ports? |
Date: | 2012-05-05 16:44:14 |
Message-ID: | 20120505164414.GA4273@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 05, 2012 at 12:08:00PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2012-05-05 20:45:15 | Re: PL/Python result set slicing broken in Python 3 |
Previous Message | Fujii Masao | 2012-05-05 16:41:39 | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |