Add feature flags for compression algorithms #241
Conversation
|
What should I do about the failing tests on |
Flag the test on the availability of the compression for now I suppose. Could you explain your motivation for the PR - is it just reducing dependencies in a use case that doesn't require them? (That's perfectly fine, I'm just curious) |
famfo
force-pushed
the
compression-featureflags
branch
from
20df642 to
1ca18c9
Compare
|
Mostly a use case that doesn't require anything else than zstd and we'd like to reduce the amount of C code we link against. |
famfo
force-pushed
the
compression-featureflags
branch
2 times, most recently
from
dd61e5f to
b7a93b9
Compare
This commit adds a feature flag for every compression algorithm. All compression algorithms are all enabled by default, but can be disabled in case they are not used to reduce the amount of dependencies.
famfo
force-pushed
the
compression-featureflags
branch
from
b7a93b9 to
98f70fa
Compare
|
Do you have more changes planned? If not I can do a new release, otherwise I can wait. |
|
Decompressing content from archives would still be nice but implementing that would probably still take a few days. |
This pull request adds a feature flag for every compression algorithm. All compression algorithms are all enabled by default, but can be disabled in case they are not used to reduce the amount of dependencies.
Please note: I couldn't run all the tests because some containers are not found in the registry I am using.