Opened 10 years ago
Closed 10 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 by , 10 years ago
Milestone: | → milestone1 |
---|
comment:2 by , 10 years ago
comment:3 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
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.
Actually, if you export from a bash shell, you should see UNIXROOT defined, e.g.:
As such, it is possible to use bash syntax:
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:
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):
And, BTW, sh behaves in the opposite manner:
All of this aside, did you really mean to open this ticket here and not here, under ports?