| From: | Mankirat Singh <mankiratsingh1315(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-www(at)lists(dot)postgresql(dot)org, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Pavlo(dot)Golub(at)gmail(dot)com |
| Subject: | Re: Development of ABI Compliance Checker for official PostgreSQL Repo |
| Date: | 2025-05-21 18:45:13 |
| Message-ID: | CAOtk82QqhAOno9NoJ3rHMY_+qUej-tJ9rT7DcQytcp7wjyzgMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Wed, 21 May, 2025, 8:22 pm Peter Eisentraut, <peter(at)eisentraut(dot)org>
wrote:
> And then you should create a suppression file so that situations like
> the above can be checked and added to an approved list.
>
Oh, I didn't knew much about suppression file in libabigail before, just
read it's documentation in detail.
Will surely look into it specifically for postgres use case and update on
it asap.
Thanks for the direction.
I think it is essential for this project that the output is empty if
> there are no problems ("no news is good news"). No one will want to dig
> through the output if it produces warnings about harmless things.
>
True that :)
Regards,
Mankirat
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Booz | 2025-05-22 17:47:01 | Wiki edit access |
| Previous Message | Peter Eisentraut | 2025-05-21 14:51:52 | Re: Development of ABI Compliance Checker for official PostgreSQL Repo |