On 20 Mar 2025, at 15:08, Graham Leggett <minf...@sharp.fm> wrote: > Ideally I would like some more up to date feedback, taking into account all > the changes up till now. Reading through the links, I recognise and have > fixed most of them, particularly with respect to the Windows build.
Further clarification is needed, I don't think my descriptions came out clearly. Apr-trunk contains a brand new LDAP API that shares zero common code, and zero compatibility with, the old APR-util v1 API. This means that httpd-trunk today (which depends on the APR-util v1 API), will not build with apr-trunk today. This is not a regression, because prior to this apr-trunk had no LDAP API at all, and so https-trunk didn't build by definition. The following PR changes httpd-trunk to use the apr-trunk API: https://github.com/apache/httpd/pull/438 APR-util v1.7 contains both the old LDAP API, and the new apr-trunk API, at the same time, so that migration is possible. This means that httpd-trunk today should be able to build with apr-util 1.7 today. To sum up: - httpd-trunk + apr-trunk - old API and new API will not build by definition. - httpd-trunk + apr-trunk + https://github.com/apache/httpd/pull/438: new API and new API will build - httpd-trunk + apr-util-1.7: old API and old+new API will build - httpd-trunk + apr-util-1.7 + https://github.com/apache/httpd/pull/438 <https://github.com/apache/httpd/pull/438:>: new API and old+new API will build Does this make sense? Regards, Graham --
