Re: static linking a library

[Neal Gompa]

On Thu, Dec 1, 2016 at 10:44 AM, Neal Becker  wrote:
> Mercurial upstream is asking about a compression library zstd.
>
> Specifically:
> https://www.mercurial-scm.org/pipermail/mercurial-packaging/2016-November/000178.html
>
> I believe the proposed solution here:
> https://www.mercurial-scm.org/pipermail/mercurial-packaging/2016-December/000182.html
>
> which is to statically link the library to the mercurial executable would
> also raise issues?  A special exception to the statically linked binary
> would be required?

Per our guidelines[1], just add a bundled(zstd) Provides that
indicates what version of the library is vendored in. And as soon as
reasonably possible, unbundle it.

That's all you need to do. I would also suggest leaving a comment in
the spec above the bundled() Provides to the discussion so that the
rationale is known and documented.

[1]: 
https://fedoraproject.org/wiki/Bundled_Libraries#Treatment_of_Bundled_Libraries


-- 
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

static linking a library

[Neal Becker]

Mercurial upstream is asking about a compression library zstd.

Specifically:
https://www.mercurial-scm.org/pipermail/mercurial-packaging/2016-November/000178.html

I believe the proposed solution here:
https://www.mercurial-scm.org/pipermail/mercurial-packaging/2016-December/000182.html

which is to statically link the library to the mercurial executable would 
also raise issues?  A special exception to the statically linked binary 
would be required?

Thanks,
Neal
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org