[Rpm-maint] [rpm-software-management/rpm] RFE: add opt-in compat defines for renamed v4 tags (Issue #3830)

[Panu Matilainen]

pmatilai created an issue (rpm-software-management/rpm#3830)

Commit f14557cd521ddf95994aa6518f006eeb3fc58d87 renamed PAYLOADDIGEST to PAYLOADSHA256 to make room for SHA3, breaking API but not ABI in the process. There are other similar renames on planned/on the way. That breakage is intentional: users of that data will need to be aware of the changes in this area, and we have no better way to do that than break the build.

We can however add opt-in compatibility through something like -D_RPM_4_COMPAT define to let other software recompiled against 6.0 with minimal effort while acknowledging the need for adjustment. Or so the theory goes. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3830
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/3830 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20250624/8df92342/attachment.htm>