Re: Have postgres.bki self-identify - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Have postgres.bki self-identify
Date
Msg-id 1117526.1742502788@sss.pgh.pa.us
Whole thread Raw
In response to Re: Have postgres.bki self-identify  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Have postgres.bki self-identify
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Mar 20, 2025 at 3:47 PM David G. Johnston
> <david.g.johnston@gmail.com> wrote:
>> While trying to find postgres.bki in my build directory searching for the file name didn't work because there is no
commentin the file containing the file name; like there is in every other file we write or generate, including the
related*_d.h files.  Add it. 

> I'm not a fan of making it a policy that everyone has to do this. I'd
> rather see us remove filenames from some places where they cause
> maintenance overhead for little benefit. If somebody wants to find
> postgres.bki, I guess you can just "find . -name postgres.bki -print"

While I don't care much about the filename per se, I do note that
we embed copyright notices into most generated files.  Why
not this one?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Not-terribly-safe checks for CRC intrinsic support
Next
From: Jacob Champion
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER