Florian

> @sushichop @ffried Thanks for doing this! It looks like in DDContextFilterLogFormatter+Deprecated.h and DDContextFilterLogFormatter+Deprecated.m still have a few places leftover that's referencing blacklist and whitelist. I know those files are...

@sushichop @dive I'd be careful with this setting. There is a lot that can go wrong when enabling this setting. I think in one of the WWDC Talks (or release...

@dive > And yes, it is mainly for binary distributions (that's the case for us, we use Carthage). In this case, Carthage is the one serving binaries - not us....

@dive Heck, let's just create that branch and see where it leads. 🙃 As long as no one requires it to be up-to-date (with `master`) at all times, this should...

@dive > I was talking about the fact that there are not much differences and side-effects when you build CocoaLumberjack together with the application you are going to ship. That...

I've marked this PR as `WIP` and added the necessary labels so this won't be marked as stale.

@dive Thanks a lot for the insights here! Very interesting to hear about the experiences in other larger scale projects! On our CI, we also do clean builds every time....

@dive >> So maybe you might also open an issue against Carthage and propose that they inject the BUILD_LIBRARY_FOR_DISTRIBUTION build setting when they build their binaries...? > I do not...

Well, OSLog is nice until you need to actually do something with the logs. Ever tried to attach them to a support request created by the user inside an app?...

Btw. since OSLog (at the moment) can't really be wrapped - due to it's static evaluation of message templates - it's not something the OpenSource community can solve.