| From: | "Larry Rosenman" <ler(at)lerctr(dot)org> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Dave Page'" <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | "'Andrew Dunstan'" <andrew(at)dunslane(dot)net>, "'Bort, Paul'" <pbort(at)tmwsystems(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Anyone still care about Cygwin? (was Re: [CORE] GPL Source and Copyright Questions) |
| Date: | 2006-06-23 14:30:14 |
| Message-ID: | 00e001c696d1$8b0241b0$0202fea9@aus.pervasive.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
>>> Actually, my gripe about this one is that it wasn't detected
>>> promptly. That patch went in two weeks ago; we should have known
>>> about
>>> the problem
>>> within a couple days at most. Seems like the Windows members of the
>>> buildfarm don't run often enough. The whole point of the buildfarm
>>> is to spot problems while the code is still fresh in mind, no?
>
>> I think that speaks for the current usage of the cygwin port. Snake
>> runs native builds daily, but like Magnus and his dev box there's no
>> way I'm letting Cygwin anywhere near it. Istr that the only vaguely
>> active Cygwin member is Andrew's laptop.
>
> Well, "lack of interest" is certainly adequate reason to decommission
> a port. If we can't find anyone who cares enough about Cygwin to
> host a regularly-scheduled buildfarm member, I'm for blowing it off.
>
What all's needed on the host for this?
I might be able to use either my house machine or my work desktop
here @pervasive, or one of my test boxes here @pervasive.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler(at)lerctr(dot)org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Woodward | 2006-06-23 14:30:15 | Re: vacuum, performance, and MVCC |
| Previous Message | A.M. | 2006-06-23 14:29:52 | Re: vacuum, performance, and MVCC |