Opened 6 years ago

Closed 6 years ago

#86 closed defect (invalid)

Our bash port is broken #2: it doesn't know anything about /@unixroot/

Reported by: dbanet Owned by:
Priority: major Milestone: milestone1
Component: rpm Version:
Severity: Keywords:
Cc:

Description

[WORKSTATION|/]cd /@unixroot/
bash.exe: cd: /@unixroot/: No such file or directory

sh works okay:

# cd /@unixroot/
#

Change History (3)

comment:1 Changed 6 years ago by dbanet

Milestone: milestone1

comment:2 Changed 6 years ago by Lewis Rosenthal

Actually, if you export from a bash shell, you should see UNIXROOT defined, e.g.:

declare -x UNIXROOT="J:"

As such, it is possible to use bash syntax:

# cd $UNIXROOT
#

Until I just tried it, I thought that it would be possible to create an alias for $UNIXROOT as /@unixroot, but unfortunately, the "/" breaks the alias functionality (nor can I export that as part of a variable). In fact, the "/" breaks $UNIXROOT, as well, as in:

# cd /$UNIXROOT/etc
bash.exe: cd: /@unixroot/etc: No such file or directory

This means that it's not just a matter of recognizing @unixroot (easily done; I can make @unixroot=$UNIXROOT), but of accepting /@unixroot (or even /J:, in my case):

# cd /J:/etc
bash.exe: cd: /J:/etc: No such file or directory

And, BTW, sh behaves in the opposite manner:

# cd /$UNIXROOT/etc
cd: can't cd to /J:/etc

All of this aside, did you really mean to open this ticket here and not here, under ports?

comment:3 Changed 6 years ago by Yuri Dario

Resolution: invalid
Status: newclosed

The current bash binary shipped with RPM is an old prebuilt binary taken from the net.
So this ticket is not valid until someone takes care of porting newer code.

And the correct trac for reporting is 'ports', this trac is only for rpm and strictly related tools.

Note: See TracTickets for help on using tickets.