bug#36416: realpath doesn't preserve '..' consistently as per POSIX, nor '/.'

[L A Walsh]

I don't recall reading anything about posix allowing the elimination
of such paths.

If I have an application layer on top of linux that processes those
double slashes, it may or may not work depending on the underlying OS?

That wouldn't be very portable w/r/t a Portable OS Information eXchange
standard.

I also specified the elimination of the single dots after a slash
which in reality don't have the same meaning as the slash.

It would useful if bugs were not closed before asking for more
information.  I've seen many bugs over the years that were closed
when they were real bugs that came back and bit the project hard,
including bugs that were closed out because I hadn't sent them through
cygwin's list first when I knew they were not bugs in cygwin.



On 2019/06/28 08:38, Eric Blake wrote:
> tag ### notabug
> thanks
> 
> On 6/28/19 6:11 AM, L A Walsh wrote:
>> realpath -m //sysname/rootdir/.
>> returns "/sysname/rootdir"  This is incorrect, according to POSIX.
> 
> No, it is implementation-defined if it is correct.  You failed to say
> what platform you are on.  If you are on Cygwin, where // is distinct
> from /, then it is incorrect - but that's not the behavior of realpath
> on Cygwin.  If you are Linux, where // is an alias for /, then the
> behavior is correct.
> 
> Unless you can provide more details about which system you saw this
> behavior on, and which version of realpath you tested, I'm marking this
> as not a bug.
>