From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | "Baker, Keith [OCDUS Non-J&J]" <KBaker9(at)its(dot)jnj(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal to add a QNX 6.5 port to PostgreSQL |
Date: | 2014-07-28 16:41:57 |
Message-ID: | CAHyXU0ykuhv0B+jZRgewV81LwFty4D4R=Mmv=76fR8Pr0YoSfA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 28, 2014 at 11:22 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2014-07-28 11:19:48 -0500, Merlin Moncure wrote:
>> Maybe step #1 is to get a buildfarm member set up. Is there any
>> policy against unsupported environments in the buildfarm? (I hope not)
>>
>> You're going to have to run it against a git repository containing
>> your custom patches. It's a long and uncertain road to getting a new
>> port (re-) accepted, but demonstrated commitment to support is a
>> necessary first step. It will also advertise support for the platform.
>
> I don't think a buildfarm animal that doesn't run the actual upstream
> code is a good idea. That'll make it a lot harder to understand what's
> going on when something breaks after a commit. It'd also require the
> custom patches being rebased ontop of $branch before every run...
hm. oh well. maybe if there was a separate page for custom builds
(basically, an unsupported section).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Fabrízio de Royes Mello | 2014-07-28 17:24:58 | Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED |
Previous Message | Christoph Berg | 2014-07-28 16:41:45 | Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED |