README and travis.yml should be linked

[calispac]

In order to guaranty that installation procedure is the same in both files we should have the README and travis.yaml linked.

I propose that the README is built from the travis.yml or the other way around (if possible).
Do you have any suggestions for that ?

[dneise]

Unfortunately I have no idea how to do this, the README is a static file.

For sphinx docu, which is build, I guess one could rig something .. but for the README, I see no nice way. A simple hyperlink into the travis.yml would be a start, I think.

I think, we struggle with this, since we try to accomplish something unusual in the Python ecosystem. Usually one would write a thing, be it an application or program or a library, which depends on other libraries. And these dependencies, one would simply note in the setup.py.

Installing the project should be: pip install
The rest is done by pip, it find the dependencies and resolves them.

This is most easy, when all dependencies are already PyPI, the Python Package Index (https://pypi.python.org/pypi).
If the dependencies themselves are only available as github repos and not available on pypi, pip in less easy to convince to resolve these dependencies ... I opened an issue about this, but must admit, I did not check for a long time, how pip behaves about this right now.

pypa/pip#3610

[calispac]

Maybe we could have test_install_script.py were we compare travis.yml and README.md
The test is then executed by pytest or travis.

[dneise]

I have no real solution for this ... but ... in principle we should try to work towards making the install as easy as: pip install digicampipe

Then this becomes a non-issue

[dneise]

I'd like to see, what is needed to make this repo even easer to install so I assign this one to me

[dneise]

Still I had no time to work on this ... volunteers to take this over?