Eric Blake wrote: > But it will obliterate /bin/sh if a user wanted it to be ksh or zsh. The > whole reason that 00bash.sh first checks what sh is currently, is > because I only want the upgrade to take place if it is ash or an > outdated bash, but to not penalize users who like ksh or zsh when > they call system() (Mac, for example, does sh == zsh, unlike Linux with > sh == bash). I'm really thinking more along the lines of:
Ah. Okay, I didn't know you were officially supporting that. I figured that anyone doing that would be used to replacing /bin/sh manually since until recently ash would have clobbered it unconditionally any time the package was updated. The two-stage should still work - I think. Brian
