From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Fetter <david@fetter.org>
cc: buildfarm-members@postgresql.org
Subject: Re: Moving to HTTPS
In-reply-to: <20170108060140.GA27033@fetter.org>
References: <89d566b4-58fb-c1e9-97ef-46d4d915b86c@dunslane.net>
 <20170107215523.GA294152@tornado.leadboat.com>
 <96080bc2-086f-c47f-6cee-b7f00a9bcd38@2ndQuadrant.com>
 <3104.1483834327@sss.pgh.pa.us> <20170108060140.GA27033@fetter.org>
Comments: In-reply-to David Fetter <david@fetter.org>
	message dated "Sat, 07 Jan 2017 22:01:40 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <14801.1483889673.1@sss.pgh.pa.us>
Date: Sun, 08 Jan 2017 10:34:33 -0500
Message-ID: <14802.1483889673@sss.pgh.pa.us>
Precedence: bulk
Sender: buildfarm-members-owner@postgresql.org

David Fetter <david@fetter.org> writes:
> On Sat, Jan 07, 2017 at 07:12:07PM -0500, Tom Lane wrote:
>> I could embark on a massive update binge, but that would sort of defeat
>> the purpose of testing against old Perl versions.  Thoughts?

> You could use install a more modern Perl version just for the
> buildfarm client while keeping the system perl marooned however far in
> the past we promise to support.  Don't know just how painful that is
> on those machines...

Yeah, I was thinking about the same: build a modern perl somewhere off to
the side (not in the normal PATH) and run the buildfarm script using that
while the build per se continues to use the system Perl.  The pain here
is going to mostly come from the buildfarm script itself, I'm afraid.
One thing I noticed right away is it's got /usr/bin/perl hardwired into
all its shebang lines.  Don't know what other gotchas there are.

			regards, tom lane


-- 
Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members