search for: mainatained

...on linux can mean one of two things; bash in bourne shell comatibility mode or dash. These two behave differently enough to make it a pain to be always testing them. The other issue is that using some bash features will allow me to reuse code and reduce the amount of shell script that needs to be mainatained. Does anyone see any major problems with this? Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

Op 25-11-14 om 23:39 schreef Jan Stary: > Is there a reason the test scripts are calling bash? The change from sh to bash was made a little more than a year ago. The mailing list thread accompanying this change can be found here: http://lists.xiph.org/pipermail/flac-dev/2013-September/004374.html

...s not mean sh(1), but one of two other shells (!), compatibility is broken for systems that either do not come with bash or install it anywhere else but /bin/bash. The other issue is that using some bash features will allow me to reuse code and reduce the amount of shell script that needs to be mainatained. Exactly which bash features are used here that sh(1) does not have, and how much of that code is reused so that it balances pissing off anything but a Linux distribution? Jan

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate snapshot of the Samba 3.0.2 code base and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and is provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at your own risk. Common bugs fixed in this preview

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate snapshot of the Samba 3.0.2 code base and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and is provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at your own risk. Common bugs fixed in this preview

...wo other shells (!), compatibility is broken > for systems that either do not come with bash > or install it anywhere else but /bin/bash. > > The other issue is that using some bash features will allow me > to reuse code and reduce the amount of shell script > that needs to be mainatained. > > Exactly which bash features are used here that sh(1) does not have, > and how much of that code is reused so that it balances > pissing off anything but a Linux distribution? The diff below makes the tests run on my system (OpenBSD), which does not have bash, and doesn't seem...