Re: prevent 006_transfer_modes.pl from leaving files behind

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: prevent 006_transfer_modes.pl from leaving files behind
Date: 2025-04-08 14:37:51
Message-ID: d9aa3820-2495-42b1-8c5a-f598be69f52c@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2025-04-08 Tu 10:17 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> On 2025-04-07 Mo 7:41 PM, Michael Paquier wrote:
>>> delete_old_cluster.sh would be left around even if not using a VPATH
>>> build with ./configure (your commit message does not mention that).
>>> Even if .gitignore discards it, the file is here.
>> I don't think that matters. In non-vpath builds we expect the source
>> directory to be scribbled on. All sorts of things might be left around.
> It's okay as long as .gitignore ignores it and "make clean" removes it.
>
> When/if we give up makefile builds, a lot of these maintenance
> issues will go away...

Maybe some will, but I observed the present issue on fairywren which is
using meson.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-04-08 14:59:25 Re: Draft for basic NUMA observability
Previous Message Bruce Momjian 2025-04-08 14:36:45 Feature freeze