On Freitag, 24. Juli 2020 18:50:47 CEST Peter Maydell wrote: > On Fri, 24 Jul 2020 at 17:46, Philippe Mathieu-Daudé <phi...@redhat.com> > wrote: > > I guess we were expecting the distrib to update the pkg. > > Apple's view is that you shouldn't be using the sasl header > at all but instead their proprietary crypto library APIs, so > I wouldn't expect them to ever ship something without the > deprecation warnings.
AFAIK Apple's reason for this is similar to no longer providing headers for OpenSSL [1] (or now actually BoringSSL): they cannot guarantee binary compatibility of these libs beyond individual macOS releases (i.e. without breaking old clients) and bad things happened [2] in the past for apps which expected it would. [1] https://lists.apple.com/archives/macnetworkprog/2015/Jun/msg00025.html [2] https://lists.andrew.cmu.edu/pipermail/cyrus-sasl/2007-November/001254.html The common recommendation is: "Ship your macOS app bundled with the preferred version of these libs." Best regards, Christian Schoenebeck
