Scripting guidelines

[Ewoud Kohl van Wijngaarden]

On Thu, Feb 20, 2014 at 09:52:23PM +0100, David Caro wrote:
> Lately I've had a hard time to properly review some patches containing shell
> scripts to manage our infrastructure because there's no guidelines. So I created
> a wiki page with a proposal [1]. It's made up as a mix of some already existing
> guidelines.
> 
> The reason to wrote a bash style guide and not a shell stile guide is because I
> think that bash is widely adopted (default GNU shell) and provides enough
> advantages to sacrifice some portability. I think that most of our maintenance
> and management scripts will never be run on non-GNU OSes.
> 
> POSIX compliance should be only used when really needed, for example, scripts to
> build a specific project, that might be run on non-GNU based systems in the far
> future.
> 
> This thread is to start a discussion about it so please, share your opinions and
> concerns (and proposals).
> 
> [1] http://www.ovirt.org/Bash_style_guide

+1 to using bash for our management scripts. We are in control of what
we run so no need for maximum portability.