• Re: [Summary]: Supporting alternative zlib implementations

    From Mark Brown@21:1/5 to Fay Stegerman on Fri Dec 6 18:20:01 2024
    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.

    -----BEGIN PGP SIGNATURE-----

    iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmdTLdUACgkQJNaLcl1U h9Dqdgf9ELjBpCUtdDkm8F/q9OuCJm5dsplPPPwh0Itzr29gx0DTotGfV+fXDdWu iJqO+hHDKIoS7mqXa2vPKMrNd4x5K5rhd7mI1imlA/ey42yEopOIs9SnEs8p1UCz yu47HjAAFu7nuVMRiphAgpgTLQedseRwIgaHsn6PDQp8xXqDrmQhRM4m5qOan7p/ nfIEoUbiObU2GGK/JDTY+tpqwnopWMu2g4WeLg2ThZVSWhDVsdbIPyKFjXB/rFGS TIPb42mn2MDH+W52zqBgN+QoR8zYkj3jZgqq5CM6+djykXRZPP7pDZ63Muv3n6Xt 8PbnVsoonitCOR0NPxiy8wbW1h5UUQ==
    =ffpQ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)