replace run_cmd/run_cmd_qa by vsc-base's run

[boegel]

We should replace the mess that is run_cmd and run_cmd_qa by the (better) equivalent provided by vsc-base, i.e. run, see https://github.com/hpcugent/vsc-base/blob/master/lib/vsc/utils/run.py

[JensTimmerman]

This should also give us live output from a command.

[mboisson]

live output would be very nice to have....

[JensTimmerman]

This is actually pretty easy to do, I once did it just for testing on my own copy of EB:
JensTimmerman@aa3f091
and JensTimmerman@ab1bd70

But I guess a lot of code has changed since then.

[boegel]

@JensTimmerman Migrating to the run support provided by vsc-base is still something we should try and do, but we should try and do that without breaking backward compatibility, e.g. run_cmd should be a wrapper around one of the run functions provided by vsc.utils.run?

[JensTimmerman]

Yes indeed, I was trying to illustrate how a few minor changes can make a real big change in user experience when running --debug to screen. So yes, please incorporate something similar into EB.

[Micket]

So run_cmd got replaced with run_shell_cmd in 5.0.x., so the original issue opened here is no longer relevant.

But perhaps we should take note of the live request here (which I assume just mean to have the stdout/stderr piped directly to the screen?)