[
https://issues.apache.org/jira/browse/MESOS-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713870#comment-13713870
]
Timothy St. Clair commented on MESOS-543:
-----------------------------------------
I did a pass through again, and prior to proper rpm-generation the 3rdparty
elements need to be broken out into separate packages, each with their own
dependency checking.
Thus libprocess (which also re-bundles) and stout would also need package
generation, and proper checks.
I'm guessing starting from here: https://github.com/3rdparty .
I can assist on the breakout and checking, but I guess a higher level question
would be, "Does anyone outside of mesos actually use these libraries?" If not,
then it may make sense to roll it all together and do one grand dep check in
mesos, and bundle under a single mesos-devel subpackage.
Thoughts?
> 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
