[jira] [Commented] (MESOS-1137) Add FAQ linked within docs/getting-started.md

["Vinod Kone (JIRA)" <ji...@apache.org>]

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

Vinod Kone commented on MESOS-1137:
-----------------------------------

I would recommend for us to just have our FAQ link to Mesos SO page http://stackoverflow.com/questions/tagged/mesos?sort=votes&pageSize=30. 

It is great for several reasons:
 
--> Automatically created/updated by the users.

--> Has votes and accepted answers.

--> Easily searchable.

> Add FAQ linked within docs/getting-started.md
> ---------------------------------------------
>
>                 Key: MESOS-1137
>                 URL: https://issues.apache.org/jira/browse/MESOS-1137
>             Project: Mesos
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Till Toenshoff
>            Priority: Trivial
>              Labels: documentation, faq, getting-started.md
>
> Experience shows that there are a few very common questions that pop up for people that start playing with mesos.
> So I would like to propose adding some kind of FAQ to our documentation. Specifically for OSX, here are some points that I collected over the time. As there will most likely be more, starting this ticket as a collection before adding an FAQ might be good to find out if it made sense having it.
> h2. OS Independent
> h4.When running {{make check}} one of the tests fails, what now?
> After the tests have been compiled, individual tests can be executed manually. 
> Lets assume that a test named {{Foo.Bar}} had failed for you. Now go ahead and run that test individually, with enhanced output:
> {{./bin/mesos-tests.sh --gtest-filter="Foo.Bar" --verbose}}
> That should reveal some more insights of the failure reasoning.
> [add some more info on how to skip tests in make check]
> h2. OSX Related
> h4.Mesos requires automake < 1.14 due to incompatibility issues
> with the 'subdir-objects' option.
> [insert link to jira ticket here]
> For installing automake 1.13.4 via homebrew:
> {{brew versions automake}}
> {quote}
> 1.14     git checkout 14a1fa8 /usr/local/Library/Formula/automake.rb
> 1.13.4   git checkout 029cdc3 /usr/local/Library/Formula/automake.rb
> 1.13.3   git checkout 9c7cf36 /usr/local/Library/Formula/automake.rb
> 1.13.2   git checkout 7f584b0 /usr/local/Library/Formula/automake.rb
> 1.13.1   git checkout 1e5eb62 /usr/local/Library/Formula/automake.rb
> 1.13     git checkout 2754bd4 /usr/local/Library/Formula/automake.rb
> […]
> {quote}
> To be on the safe side, we may now uninstall any automake versions that was previously installed using homebrew.
> {{brew uninstall automake}}
> You may install 1.13.4. To do so, git-checkout the homebrew formula for that specific version manually.
> {{cd /usr/local/Library/Formula/}}
> {{git checkout 029cdc3 /usr/local/Library/Formula/automake.rb}}
> Now we can simply install automake, the manually chosen version will be used instead of the most recent one.
> {{brew install automake}}
> h4.Could not link test program to Python.
> [insert link to jira ticket here]
> You may have installed a Python version that did not come with OSX by default (e.g. via MacPorts or Homebrew). If that is the case, make sure the version used is 2.7.3. Anything more recent up until and including 2.7.6 will cause this problem. 
> *Note:* This does not apply for the default Python that is delivered by Apple (currently 2.7.5). Apple has fixed this problem in their distribution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)