Comment 4 for bug 2037584

Speaking for myself as a member of the SRU team, and not the SRU team as a whole:

It seems to me that since pkgbinarymangler is designed to do multiple things, some of which we have no reason to disable, we should aim to disable just the translation handling since that's exactly what we want to do. And the package has a mechanism to do that so we should use it. Even if a little unwieldy by requiring a pkgbinarymangler upload, using this mechanism seems like it would be relatively risk-free in an SRU because it is very specifically targetted. Even if it does potentially impact every build, its behaviour should be able to be fairly easily checked. We could verify that its behaviour hasn't changed against an unrelated package during SRU verification easily and confidently enough. Using NO_PKG_MANGLE sounds like it has other side effects that might have more implications that need consideration and therefore more risk of missing something.

For the development release, perhaps a finer-grained control in pkgbinarymangler that can be operated from the build of a package itself rather than changing pkgbinarymangler would be appropriate. But for an SRU I think using striptranslations.blacklist seems like the minimally impactful way to do it.