public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: David E. Wheeler <[email protected]>
To: Mankirat Singh <[email protected]>
Cc: [email protected]
Cc: [email protected] <[email protected]>
Subject: Re: Development of ABI Compliance Checker for official PostgreSQL Repo
Date: Mon, 19 May 2025 16:17:24 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAOtk82TM4W4r50f38yG84Q8QkM216kebniqVid+k9XaEoNb-Vg@mail.gmail.com>
	<[email protected]>

On 18.05.25 20:29, David E. Wheeler wrote:
> On May 16, 2025, at 02:42, Mankirat Singh <[email protected]> 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/
> 

view thread (12+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Development of ABI Compliance Checker for official PostgreSQL Repo
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox