Feedback-ID: ie0a040ee:Fastmail
Message-ID: <f27ff897-c0e4-440d-9dfa-c72ad589ecea@eisentraut.org>
Date: Mon, 19 May 2025 16:17:24 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Development of ABI Compliance Checker for official PostgreSQL
 Repo
To: "David E. Wheeler" <david@justatheory.com>,
 Mankirat Singh <mankiratsingh1315@gmail.com>
Cc: pgsql-www@lists.postgresql.org,
 "Pavlo.Golub@gmail.com" <Pavlo.Golub@gmail.com>
References: 
 <CAOtk82TM4W4r50f38yG84Q8QkM216kebniqVid+k9XaEoNb-Vg@mail.gmail.com>
 <F92EE592-ED82-47A0-A6A0-B4AD4539560A@justatheory.com>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: <F92EE592-ED82-47A0-A6A0-B4AD4539560A@justatheory.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/f27ff897-c0e4-440d-9dfa-c72ad589ecea%40eisentraut.org>
Precedence: bulk

On 18.05.25 20:29, David E. Wheeler wrote:
> On May 16, 2025, at 02:42, Mankirat Singh <mankiratsingh1315@gmail.com> wrote:
> 
>> I had wrote two blogs for the same discussing about importance of this project and how I plan to work on this at blog.mankiratsingh.com I’d greatly appreciate any feedback or suggestions.
> 
> Anyone have thoughts on Mankirat’s proposal[1] to start with libabigail’s abidiff utility to produce the the raw data for each report, and then write Perl code to transform it to a publishable report?

Well, normally (if there are no problematic ABI changes) the report will 
be empty.  So I wouldn't spend too much time on the formatting.  If 
there is a violation, you can just show the raw abidiff output inside 
<pre> or whatever.

Generally, this looks like the right direction.

As an additional tip, check the Python source code, they are doing 
something like that with libabigail as well.

> 
> Best,
> 
> David
> 
> [1]: https://blog.mankiratsingh.com/posts/abi-compliance-reporting-part-2/
>