Handling incompatibilities with App Store review processes

[ncoghlan (Alyssa Coghlan)]

@gpshead

Sure, there will be other distibutors as well, but given this a common need among all of them, maintaining the patches to apply as part of the config/build process when targeting the platform within our project tree makes sense.

Does that mean it’s time to paint a config option bikeshed?

--with-app-store-patch feels both a bit broad (not scoped to iOS), but also a bit narrow (“patch” specifies a mechanism rather than an intent).

Would --with-ios-app-store-compliance work? That way it would cover anything that was found necessary to produce runtime binaries that pass iOS app store compliance checks, whether those are patches, other build options, or anything else that comes up.

@ronaldoussoren

One thing I haven’t looked into for this particular issue is there is a way to reimplement parse.py in such a way that mentioning the problematic string is no longer necessary. That said, it is unlikely that this is possible due to uses_netloc being effectively public API.

I did spend a little bit of time looking at that, but didn’t see anything obvious that wasn’t a variant on obfuscating the text string in a way that would keep it in separate pieces in the pyc file (e.g. writing it as "-".join("itms", "services") rather than as a regular string literal, although I’m not sure even that would be enough to confuse the AST optimiser these days)