There is one more DASH bug.
Described here:
http://groups.google.com/group/vim_use/browse_thread/thread/837988813a06c280/f8b4aadd575affaa?lnk=gst&q=expect#f8b4aadd575affaa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
If GDM is sourcing the user's setup files using any shell other than the
user's defined shell (from getpwent() or whatever) then that's a bug in
GDM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14148
At the very least, Ubuntu should make sure user's rc scripts
(~/.profile, which sources ~/.bashrc for instance) does not contain
dash-incompatible code by default, as it currently does. Programs like
gdm source those but are run from dash resulting in user's stuff not
being sourced before startup
Not really wanting to get into this debate, but having had my tutorial
linked here and associated with an opinion, I must clarify that my ideal
for UNIX and Linux systems is that /bin/sh be in some way consistent,
and provide all Bourne functionality. That is, my personal view is that
stating "#!/b
Temporary tricks for running an sh scripts
http://liquidweather.net/howto/index.php?id=59
--
dash as #!/bin/sh introduces countless incompatibilities
https://bugs.launchpad.net/bugs/141481
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is also being discussed on http://brainstorm.ubuntu.com/idea/2225/
- make your vote count ;-)
--
dash as #!/bin/sh introduces countless incompatibilities
https://bugs.launchpad.net/bugs/141481
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have written https://wiki.ubuntu.com/DashAsBinSh (a new version, to
replace the spec that used to be there) to address many of these issues,
and linked it from the Edgy release notes.
As far as non-POSIX constructs go, Paul Smith is right on the money with
his comments in
https://bugs.launchpad.
First, we have to make a distinction between the issues described here
which are POSIX and which mean that there is a bug in dash that should
be fixed, and those which are NOT POSIX, of which, contrary to the
assertion above, there are definitely some. For example:
$ dash -c 'a=water;echo ${a:2:2
POSIX compliance is exactly the heart of this. Just because dash *claims* to
comply
with the standard doesn't necessarily mean that it *actually* does.
Specifically, as quoted in bug #92189, section 2.6.4 of IEEE 1003.1 states
If the shell variable x contains a value that forms a valid int
The scripts *are* buggy. dash is POSIX-compliant, so all POSIX-compliant
scripts will work with it. If they use bash-specific features, they must
specify that they are to be executed by /bin/bash, rather than a general
POSIX-compliant shell.
** Changed in: dash (Ubuntu)
Status: New => Inval
10 matches
Mail list logo
