Scripting guidelines

[David Caro]

Hi everyone!

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

Cheers!

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Email: dcaro at redhat.com
Web: www.redhat.com
RHT Global #: 82-62605

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20140220/261d5af1/attachment.sig>