Return-Path: X-Original-To: apmail-mesos-dev-archive@www.apache.org Delivered-To: apmail-mesos-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2071B102B5 for ; Tue, 25 Mar 2014 01:25:57 +0000 (UTC) Received: (qmail 37945 invoked by uid 500); 25 Mar 2014 01:25:53 -0000 Delivered-To: apmail-mesos-dev-archive@mesos.apache.org Received: (qmail 37744 invoked by uid 500); 25 Mar 2014 01:25:51 -0000 Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list dev@mesos.apache.org Received: (qmail 37540 invoked by uid 99); 25 Mar 2014 01:25:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Mar 2014 01:25:46 +0000 Date: Tue, 25 Mar 2014 01:25:46 +0000 (UTC) From: "Timothy St. Clair (JIRA)" To: dev@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MESOS-1071) Enable building against installed third-party dependencies. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)