On Sun, Nov 24, 2024 at 02:06:37AM +0100, Fay Stegerman wrote: > For example, if it can be made easy to install both and choose between zlib and > zlib-ng at runtime, so it's easy to build APKs using either zlib or zlib-ng as > needed, downstream breakage can be avoided. Considering whether that can > reasonably be done doesn't seem like an unreasonable request to me. > What I would like is to be able to continue to use Debian for Reproducible > Builds regardless of what Google does or doesn't do. Right now that means being > able to choose to keep using the original zlib for backwards compatibility. If > Google switched to zlib-ng I would be asking if Debian could provide a way to > opt in to using that instead. TBH the whole situation here seems incredibly fragile - you're also vulnerable to someone making an improvement in the zlib compression code and changing the generated output that way. It feels like the wrong question is being asked here.
Attachment:
signature.asc
Description: PGP signature