haha yeah, I've never figured out best practices for dependencies' features. Do you think there's a reason we should forward this feature but not every other feature of all our dependencies? (I know that crates will often instead depend directly on flate2 and specify the features themselves)
Ah, but we're already doing this with the other deflate backends. Then this fits. You'll need to add deflate-zlib-ng to the configuration gates, otherwise the crate wont enable support properly. We need tests to pass with cargo test --no-default-features --features deflate-zlib-ng
I already send this PR: https://github.com/zip-rs/zip/pull/361 that's also adds the configuration gates. And I will also run tests with this feature flag.
haha yeah, I've never figured out best practices for dependencies' features. Do you think there's a reason we should forward this feature but not every other feature of all our dependencies? (I know that crates will often instead depend directly on
flate2
and specify the features themselves)Ah, but we're already doing this with the other
deflate
backends. Then this fits. You'll need to adddeflate-zlib-ng
to the configuration gates, otherwise the crate wont enable support properly. We need tests to pass withcargo test --no-default-features --features deflate-zlib-ng