[ https://issues.apache.org/jira/browse/MESOS-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922972#comment-13922972 ]
Till Toenshoff commented on MESOS-1071: --------------------------------------- Good point, indeed. I have proposed a way to fix MESOS-550 then that should comply with this scheme. > 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 > > 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)