[jira] [Commented] (MESOS-1776) --without-PACKAGE will set incorrect dependency prefix

["Kamil Domański (JIRA)" <ji...@apache.org>]

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

Kamil Domański commented on MESOS-1776:
---------------------------------------

[~tstclair], I'd like some feedback on whether the ability to provide a prefix for unbundled dependencies is necessary. The current method for providing the prefix is a bit unusual and conflicts with canonical usage of *\-\-with-X* and *\-\-without-X* flags.

A workaround is possible by checking for the variables in question being equal to "*no*" and changing their values to "*/usr*" in such cases. However, I see removal of prefixing altogether as a preferred solution.

Either way, I'd like to take care of this as as soon as I'm pointed in the right direction.

> --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)