On Sat, Oct 9, 2010 at 10:32 AM, Tor Lillqvist <tlillqv...@novell.com> wrote: >> Personal, but valid. To test that you actually don't introduce bashisms >> in a script you can simply set env variable POSIXLY_CORRECT=1 and then >> the bash when invoked as /bin/sh will behave as a strict posix shell. > > Unfortunately that doesn't work well enough- Even with POSIXLY_CORRECT=1 some > bashisms work without any warning message. Yeah, so one kinda is left > ondering what the point with POSIXLY_CORRECT is then. > > I found this useful script: > http://ftp.openbsd.org/ports/sysutils/checkbashisms/files/checkbashisms.pl . > No doubt there might be other similar ones. > > Another way is to actually develop a script using a #! line referring to some > suitably limited shell on your platform, and then change that to /bin/sh > before submitting s a patch or committing to git.
Just to clarify: I posted the script, as I thought it might be useful to someone else. But I did not intend to commit it to git (If I did, the post to the ML would have been in the form of a patch) Norbert. > > --tml > > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
