mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy St. Clair (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-1071) Enable building against installed third-party dependencies.
Date Tue, 25 Mar 2014 01:25:46 GMT

    [ https://issues.apache.org/jira/browse/MESOS-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945969#comment-13945969
] 

Timothy St. Clair edited comment on MESOS-1071 at 3/25/14 1:24 AM:
-------------------------------------------------------------------

Comments re above: 

1. --disable-bundled is concise and simple imo, but again I don't really have strong opinions.
 Eventually one would hope it could become the default.

2. auto-fallback when --disable-bundled is specified doesn't make sense to me, and from a
packagers perspective is unkosher.

3. How about just:
    --with-zookeeper=path 
    --without-zookeeper 
    using the previously outlined semantics.  



was (Author: tstclair):
Comments re above: 

1. --disable-bundled is concise and simple imo, but again I don't really have strong opinions.
 Eventually one would hope it could become the default, and upstream would no londer 

2. auto-fallback when --disable-bundled is specified doesn't make sense to me, and from a
packagers perspective is unkosher.

3. How about just:
    --with-zookeeper=path 
    --without-zookeeper 
    using the previously outlined semantics.  


> Enable building against installed third-party dependencies.
> -----------------------------------------------------------
>
>                 Key: MESOS-1071
>                 URL: https://issues.apache.org/jira/browse/MESOS-1071
>             Project: Mesos
>          Issue Type: Improvement
>          Components: build
>            Reporter: Benjamin Hindman
>         Attachments: modified_tillt.patch
>
>
> Most of our third-party dependencies are included in the project and statically linked
into our resulting binaries and libraries. We would like to enable building Mesos but using
system installed dependencies instead.
> In certain circumstances this is more difficult because we've actually needed to "patch"
these libraries (either for C++11 or to alter semantics).
> Rather than eliminating our internal copies of these third-party dependencies the first
step should be to just enable using external (i.e., system installed) dependencies. We already
do this for ZooKeeper by allowing people to use the --without-included-zookeeper flag during
compilation. We should do this for other libraries as well. In fact, for the libraries that
we have not patched (and even for some that we have patched) we should check to see if an
appropriate system installed dependency exists and preferentially use that unless --with-included-dependency
is explicitly used.
> Note that this issue represents a stepping stone to removing our third-party dependencies
from our repository.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message