Flawless git clone sequence

[FMassin]

• clone in target dirs (all git clone commands now run with a simple copy and paste, cd ../../ was missing before in 2nd block, and it was too many cd anyway :)
• clone a tagged SeisComP release (I also suggest adding a note on compatible SeisComP tags).

[damb]

Actually the installation instructions were never intended to be simply copy-pastable. While writing the guide I simply followed the approach @luca-s used for scrtdd.

Perhaps, it would be even more intuitive to completely refer to the SeisComP installation documentation, document the SeisComp submodules which are mandatory, and document the git clone command w.r.t. scdetect.

[damb]

BTW, is there a reason to check out a specific tag?

[FMassin]

Yes so that user compiles a version of SeisComP that has been tagged. Intermediary versions in between tags are not released.

[FMassin]

Perhaps, it would be even more intuitive to completely refer to the SeisComP installation documentation, document the SeisComp submodules which are mandatory, and document the git clone command w.r.t. scdetect.

That is too bad because scdetect doesn't need all the stuff (seiscomp sub-modules) to be compiled, it just needs what included in the readme...

[damb]

Yes so that user compiles a version of SeisComP that has been tagged. Intermediary versions in between tags are not released.

That sounds reasonable. Though, I wouldn't specify version 5.3.0 explicitly. This would require to update the installation instructions with every SeisComP release. Instead, I'd go with something like e.g. X.Y.Z including a comment to specify the desired release version.

[FMassin]

Hello!

Ok here it is :)