Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#56 closed defect (invalid)

bash fails to execute rexx scripts: OS/2 extended shebang lines

Reported by: Elmar Stellnberger Owned by: Yuri Dario
Priority: major Milestone:
Component: rpm Version:
Severity: Keywords:


The current state is that I can execute *.cmds on my path under cmd.exe only and files with shebang line (!#/bin/..) under bash only. That seems reasonable at a first glance as cmd.exe can not understand shebang lines and thus simply ignores these files as expected. However when bash comes to find a *.cmd on its path it seems to look for a shebang line instead of a rexx strarter line (/* .. */) only and thus failes if a *.cmd is on path in a cryptic way: "unknown command ." or "unknown command E:\" or anything that way.
One way out would be to make bash simply ignore *.cmds which would however disappoint me as I would like to use a certain collection of rexx-scripts also under bash.
A better way would be to either check for the suffix (*.cmd) or to recognize rexx starter lines (/* ... */) in addition to shebang lines (#!/...).
As things are implemented now I have to drop every folder which contains any *.cmd on bash startup from $PATH in .bashrc which is definitely not good.

Change History (2)

comment:1 Changed 7 years ago by Yuri Dario

Resolution: invalid
Status: newclosed

bash package is based on an existing bash port, not working with most scripts. Try ash instead.

comment:2 Changed 7 years ago by Yuri Dario

Please post only rpm, yum or python bugs here, everything else in ports trac.

Note: See TracTickets for help on using tickets.