[
https://issues.apache.org/jira/browse/MESOS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131736#comment-14131736
]
Timothy St. Clair edited comment on MESOS-1776 at 9/12/14 4:48 PM:
-------------------------------------------------------------------
--with-package= is the resolved mechanics for the situation described, and is
consistent.
If you wanted to, we could add an option such as '--disable-bundled=soft|hard'
Where soft fails over to bundled if dependency is not found, while hard just
fails when not found.
Also --without-package should probably yield a meaningful error message.
was (Author: tstclair):
--with-package= is the resolved mechanics for the situation described, and is
consistent.
If you wanted to, we could add an option such as '--disable-bundled=soft|hard'
Where soft fails over to bundled if dependency is not found.
Also --without-package should probably yield a meaningful error message.
> --without-PACKAGE will set incorrect dependency prefix
> ------------------------------------------------------
>
> Key: MESOS-1776
> URL: https://issues.apache.org/jira/browse/MESOS-1776
> Project: Mesos
> Issue Type: Bug
> Components: build
> Affects Versions: 0.20.0
> Reporter: Kamil Domański
> Labels: build
>
> When disabling a particular bundled dependency with *--without-PACKAGE*, the
> build scripts of both Mesos and libprocess will set a corresponding variable
> to "no". This is later treated as prefix under which to search for the
> package.
> For example, with *--without-protobuf*, the script will search for *protoc*
> under *no/bin* and obviously fail. I would propose to get rid of these
> prefixes entirely and instead search in default locations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
