[
https://issues.apache.org/jira/browse/MESOS-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947159#comment-13947159
]
Adam B commented on MESOS-1071:
-------------------------------
I like --disable-bundled as long as it doesn't fallback to bundled (since
they're supposed to be disabled).
However, I wonder if --disable-bundled with no fallback addresses Vinod's
comment that "I would prefer to also have an option to always use bundled
dependencies irrespective of system installed ones. In fact this could be the
default so as to not break users that are already expect this behavior. After a
deprecation period we could change the default to prefer system installed
dependencies."
I guess --enable-bundled is the default now, but any --with-XYZ=path parameters
will override it for that library. Do we have a need for a --force-bundled that
will ignore --with-XYZ parameters? I doubt it, so I'm +1 on using
--disable-bundled that does not fallback to bundled.
The only other question is how to address Till's point (d), for example, if I
want to tell Mesos to auto-detect the system path for one specific lib, but use
bundled for the rest. Right now, you would have to either --disable-bundled for
all libraries or explicitly specify the path. Or can you just set
--with-included-leveldb=no?
> 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)
