On 2022-01-09 Zakaria via Exim-users <[email protected]> wrote: >> On 9 Jan 2022, at 11:44, Jeremy Harris via Exim-users <[email protected]> >> wrote: >> On 08/01/2022 18:30, Edwin Balani via Exim-users wrote: >>> Can't you rely on OPENDMARC_LIB_VERSION? It's defined in dmarc.h:
>> Quite possibly. Now, is the changed API documented? Or are we >> supposed to inspect the libdmarc code and watch for API-breaking >> changes, evermore? [...] > I spent an amount of time trying to get latest DMARC work against master > EXIM, over last few weeks. It was only one method DMARC has refactored, with > extra parameter, and EXIM integration isn’t it taking into account. > I found this bug issue opened on > https://github.com/trusteddomainproject/OpenDMARC/issues/167 [...] Hello, Well, it does not build a lot of trust in the maintainance of the shared library if a change which breaks both API and ABI ends up in a stable release and a bugreport does not get any response. I can understand Jeremy's reluctance here. Please note that this is not completely fixable on exim's side, a exim binary built against OpenDMARC 1.3 will (probably) crash when OpenDMARC is upgraded to 1.4 without rebuilding all reverse dependencies. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
