Scripting guidelines

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RE47plWHKalNvsdv6IufdR6lM23VDXwtV Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi everyone! Lately I've had a hard time to properly review some patches containing sh= ell 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 ex= isting guidelines. The reason to wrote a bash style guide and not a shell stile guide is bec= ause I think that bash is widely adopted (default GNU shell) and provides enough= advantages to sacrifice some portability. I think that most of our mainte= nance and management scripts will never be run on non-GNU OSes. POSIX compliance should be only used when really needed, for example, scr= ipts to build a specific project, that might be run on non-GNU based systems in t= he far future. This thread is to start a discussion about it so please, share your opini= ons and concerns (and proposals). [1] http://www.ovirt.org/Bash_style_guide Cheers! --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Email: dcaro(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 --RE47plWHKalNvsdv6IufdR6lM23VDXwtV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" --RE47plWHKalNvsdv6IufdR6lM23VDXwtV--