>[1] https://github.com/facebook/zstd/issues/395#issuecomment-535875379 > ..... >If that was part of zstd or even actively being looked at, then yes. I mean, per your own comment on that thread, the API *is* available and it's in zstd, but no frontend supports it yet. And per the maintainer's comment (https://github.com/facebook/zstd/issues/395#issuecomment-492741194) the only thing preventing it from becoming more official, is being "battle-tested", which means shipping a frontend that does use it (perhaps a third-party one until it's stabilized completely) and getting people to use it. They directly compare it to a chicken-and-egg problem (https://github.com/facebook/zstd/issues/395#issuecomment-492808642) and say that there's nothing more to do upstream until that happens. And per the last comment in that thread (https://github.com/facebook/zstd/issues/395#issuecomment-974796390), there is a suggestion that the frontends already exist, it's just that nobody distributes them yet, and that making that happen could expedite the process. So I guess I'm confused about what the blocker is? If Fedora wants seekable zstd, then Fedora can make it happen by being the head on the spear. -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
