You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Till Toenshoff (JIRA)" <ji...@apache.org> on 2018/06/15 01:59:00 UTC

[jira] [Commented] (MESOS-8988) Allow for unbundled dependencies.

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

Till Toenshoff commented on MESOS-8988:
---------------------------------------

To allow for small steps in unbundling  - I converted this issue to an epic.

> Allow for unbundled dependencies.
> ---------------------------------
>
>                 Key: MESOS-8988
>                 URL: https://issues.apache.org/jira/browse/MESOS-8988
>             Project: Mesos
>          Issue Type: Epic
>          Components: build
>            Reporter: Till Toenshoff
>            Priority: Blocker
>              Labels: build,, cmake
>
> Our CMake setup currently bundles all dependencies and does not allow for building against unbundled dependencies.
> We should allow for unbundled dependencies as well.
> Motivation; 
> a. It has proven to be problematic to enforce building against the bundled versions of our dependencies. Bundled versions may or may not be compatible with all of our supported platforms. Namely Libevent >= 2.1.x fails our libprocess tests on macOS and Ubuntu 17. This in turn prevents us from switching to SSL by default on all platforms.
> b. Historically we tried to not enforce bundling and therefor allowing linux distros to supply Mesos packages. 
> c. Module authors need to link against the exact same dependency versions, where needed. Our autotools setup specifically allows for using unbundled dependencies, supporting module authors to cover this task.
> Offering bundled dependencies is per-se a good thing as it eases the pain building Mesos - we just need to make that optional.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)