[ 
https://issues.apache.org/jira/browse/MESOS-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy St. Clair updated MESOS-543:
------------------------------------

    Description: 
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

Separate fedora related packaging is being driven through: 
https://fedoraproject.org/wiki/Big_data_SIG (terrible catch all name) 


  was:
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 


    
> 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
> Separate fedora related packaging is being driven through: 
> https://fedoraproject.org/wiki/Big_data_SIG (terrible catch all name) 

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

Reply via email to