packaging hg + zstd for Fedora

Gregory Szorc gregory.szorc at gmail.com
Mon Apr 8 10:00:53 EDT 2019


Static linking to get the “advanced” zstd C API is still required. Supposedly the API will be stabilized in the next major release of zstd.

python-zstandard doesn’t support non-static linking. There is a setup.py option to not use the bundled zstd library, which is better for packagers, but still not great, since distros have an obsession with dynamic linking.

zstd is not required for Mercurial. But it makes the experience much better.

> On Apr 8, 2019, at 15:43, Neal Becker <ndbecker2 at gmail.com> wrote:
> 
> Augie Fackler wrote:
> 
>> Greg? You're the python-zstd maintainer: is the interface stable enough we
>> can support non-vendored zstd at this point?
>> 
>> Context for Neal: there at least used to be some unstable APIs in play
>> that required static linking, so our old guidance was to only use the
>> vendored zstd. I don't know offhand if that's resolved.
>> 
> 
> Hopefully static linking is not required, that would require more requests 
> for exceptions to Fedora policy.
> 
>>> On Apr 8, 2019, at 07:43, Neal Becker <ndbecker2 at gmail.com> wrote:
>>> 
>>> Hi, I'm helping to maintain hg on Fedora.
>>> 
>>> Fedora has a policy of using system libraries where possible.
>>> 
>>> Fedora currently has libzstd (1.3.8), but does not appear to have
>>> python2- zstd module.
>>> 
>>> I think we need to build hg to use the system libzstd, and to also
>>> package python2-zstd seperately.
>>> 
>>> Does this plan sound OK?
>>> 
> mercurial-scm.org/mailman/listinfo/mercurial-devel
> 
> 
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


More information about the Mercurial-devel mailing list