[
https://issues.apache.org/jira/browse/MESOS-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713881#comment-13713881
]
Benjamin Hindman commented on MESOS-543:
----------------------------------------
There is at least 1 other production user that I know about using libprocess
and stout from github.com/3rdparty. That user also embeds the libraries
directly. There are probably other tinkers. Note that 'stout' is a header only
library. In addition, we have a patch for our libev dependency. :(
IMHO, a first step would be just to provide packages for the community, even if
they're bloated (i.e., include lots of dependencies). Then we can swing back
and pull out dependencies as we are able. Likewise, I think a switch to cmake
would be rather disruptive right now. This seems like a better conversation
after other lower hanging fruit is out of the way (like packages!).
Thanks [~tstclair] and [~berngp]!
> proper auto-tools dependency checking
> -------------------------------------
>
> Key: MESOS-543
> URL: https://issues.apache.org/jira/browse/MESOS-543
> Project: Mesos
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.12.0
> Reporter: Timothy St. Clair
> Labels: build
> Fix For: 0.14.0
>
>
> Currently mesos repo includes direct version dependencies in tarballs and
> does not do proper m4 system dependency checking by default && optional
> --with(ver). That is the standard practice for downstream channel adoption.
> For more details see:
> https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
