[
https://issues.apache.org/jira/browse/MESOS-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072150#comment-14072150
]
Timothy St. Clair edited comment on MESOS-1633 at 7/23/14 7:00 PM:
-------------------------------------------------------------------
By default, every distribution (Debian, RH, Gentoo, et all) can not build
static libraries unless there is a separate -static subpackage which is
considered bad form unless it is a rebuild package such as libev.
This is the same bundling constraint I've mentioned before. Distributions
*will not rebundle*, as it is untenable to manage.
For example, imagine if everyone statically linked some version of openssl,
then a security CVE came out. You would literally need to grok (N) packages,
vs. update once.
In general, it's a bad practice.
was (Author: tstclair):
By default every distribution (Debian, RH, Gentoo, et all) can not build static
libraries unless there is a separate -static subpackage which is considered bad
form it is a rebuild package such as libev.
This is the same bundling constraint I've mentioned before. Distributions will
not rebundle, as it is untenable to manage.
For example, imagine if everyone statically linked some version of openssl,
then a security CVE came out. You would literally need to grok (N) packages,
vs. update once.
In general it's a bad practice.
> Create a static mesos library
> -----------------------------
>
> Key: MESOS-1633
> URL: https://issues.apache.org/jira/browse/MESOS-1633
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: Vinod Kone
>
> Sometimes, framework writers (e.g., C++) would like to statically link
> libmesos into their scheduler/executor to tightly control the version of
> libmesos that they depend on. While, they can bundle the libmesos.so with
> scheduler/executor it is convenient to give them access to a static library
> (e.g.: they want to create a static scheduler/executor libs).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
