You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Bernardo Gomez Palacio (JIRA)" <ji...@apache.org> on 2013/07/12 19:51:49 UTC

[jira] [Comment Edited] (MESOS-543) proper auto-tools dependency checking

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

Bernardo Gomez Palacio edited comment on MESOS-543 at 7/12/13 5:50 PM:
-----------------------------------------------------------------------

I think this effort should be related to [MESOS-73|https://issues.apache.org/jira/browse/MESOS-73]. As mentioned in MESOS-73 I created the repo [incubator-mesos-rpm|https://github.com/Guavus/incubator-mesos-rpm/blob/master/templates/apache-mesos.spec.in]. Such repo helps me create RPMs of any given commit or branch on mesos, those are named _build  spaces_ by the scripts, which I think is useful given the agility of the Mesos project.

I would like to help, so in a nutshell..
[RPM SPEC file|https://github.com/Guavus/incubator-mesos-rpm/blob/master/templates/apache-mesos.spec.in] : Please note that its an ini file configured by the _autotools_ but looking beyond that it defines a structure, see the {{%files}} section. My intention is to provide three packages inside the same RPM to install _master_, _slave_, or _local_.

Some additional files related to this effort stored in a fork of the Mesos project at [Mesos Fork|https://github.com/Guavus/incubator-mesos/tree/support/guavus-master].

[src/deploy/mesos-profile-env.sh.in|https://github.com/Guavus/incubator-mesos/blob/support/guavus-master/src/deploy/mesos-profile-env.sh.in]
[src/deploy/mesos-locald.sh.in|https://github.com/Guavus/incubator-mesos/blob/support/guavus-master/src/deploy/mesos-locald.sh.in]
[src/deploy/mesos-masterd.sh.in|https://github.com/Guavus/incubator-mesos/blob/support/guavus-master/src/deploy/mesos-masterd.sh.in]
[src/deploy/mesos-slaved.sh.in|https://github.com/Guavus/incubator-mesos/blob/support/guavus-master/src/deploy/mesos-slaved.sh.in]

For the moment I stopped working on this at least for the next two weeks, after that I will pick it up again. In the time being please let me know any feedback and hope this helps bootstrap ideas.

                
      was (Author: berngp):
    I think this effort should be related to [MESOS-73|https://issues.apache.org/jira/browse/MESOS-73]. As mentioned in MESOS-73 I created the repo [incubator-mesos-rpm|https://github.com/Guavus/incubator-mesos-rpm/blob/master/templates/apache-mesos.spec.in]. Such repo helps me create RPMs of any given commit or branch on mesos, those are named _build  spaces_ by the scripts, which I think is useful given the agility of the Mesos.

I would like to help, so in a nutshell..
[RPM SPEC file|https://github.com/Guavus/incubator-mesos-rpm/blob/master/templates/apache-mesos.spec.in] : Please note that its an ini file configured by the _autotools_ but looking beyond that it defines a structure, see the {{%files}} section. My intention is to provide three packages inside the same RPM to install _master_, _slave_, or _local_.

Some additional files related to this effort stored in a fork of the Mesos project at [Mesos Fork|https://github.com/Guavus/incubator-mesos/tree/support/guavus-master].

[src/deploy/mesos-profile-env.sh.in|https://github.com/Guavus/incubator-mesos/blob/support/guavus-master/src/deploy/mesos-profile-env.sh.in]
[src/deploy/mesos-locald.sh.in|https://github.com/Guavus/incubator-mesos/blob/support/guavus-master/src/deploy/mesos-locald.sh.in]
[src/deploy/mesos-masterd.sh.in|https://github.com/Guavus/incubator-mesos/blob/support/guavus-master/src/deploy/mesos-masterd.sh.in]
[src/deploy/mesos-slaved.sh.in|https://github.com/Guavus/incubator-mesos/blob/support/guavus-master/src/deploy/mesos-slaved.sh.in]

For the moment I stopped working on this at least for the next two weeks, after that I will pick it up again. In the time being please let me know any feedback and hope this helps bootstrap ideas.

                  
> 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