[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ash vs. bash (was: IFS behaviour)



> I would really like that we didn't let the discussion fade away and we
> came out with either a 'yes' or 'no' answer. I have now been running
> with /bin/sh -> /bin/ash for a couple of weeks now, both on test and
> on productions systems, across a few apt-get and dselect, and the only
> problems that I had were (predictably) with scripts that begin with
> #!/bin/sh and then use bash constructs like the tilde expansion for
> user homes (~user), arithmetic forms like $((...)) and name expansions
> {a,b,c}.

ash understands ~user and $((...)).  It doesn't understand {a,b,c}.
It also doesn't understand [ "$FOO" == bar ].

The fear of having /bin/sh -> ash in potato is that stuff may still
break, but I think that if we make that change now, most of the
problems should be ironed out during the freeze period.

   Julian

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
        Debian GNU/Linux Developer,  see http://www.debian.org/~jdg


Reply to: