Re: pgsql: Check that we have a working tar before trying to use it

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Check that we have a working tar before trying to use it
Date: 2021-12-14 05:17:25
Message-ID: Ybgo5ZWgqeUeW79F@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Dec 13, 2021 at 11:47:36AM -0500, Andrew Dunstan wrote:
> No. The code only sets them if they have not been previously set by
> buildenv.pl or the calling environment. That's what "||=" means.

Well, using ||= after the fact means that it is not possible to delete
any of those environment variables either in buildenv.pl, nor is it
possible to set them to empty string values, as vcregress.pl would
just reset them to the default value. And that's the case I am
arguing for here. We don't have any need to drop those default values
at all. What I am arguing for here is the possibility to have
something more flexible than what HEAD proposes.

So, if we do something like say the attached, then it is possible to
handle environments like mine, while keeping the flexibility you are
looking for to set those defaults. So that would be the best of both
worlds, no?. I also think that we had better document all that
properly, as we do for any other TAP-related variable that can be used
in vcregress.pl. All that leads me to the attached.
--
Michael

Attachment Content-Type Size
win32-perl.patch text/x-diff 2.7 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2021-12-14 14:14:08 Re: pgsql: Check that we have a working tar before trying to use it
Previous Message Michael Paquier 2021-12-14 02:00:44 Re: pgsql: isolationtester: append session name to application_name.