On Mon, Jul 28, 2014 at 11:22 AM, Andres Freund <and...@2ndquadrant.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
