Re: Stumbled upon relative name resolution across symlinks

[cyg Simple <cygsimple@gmail.com>]

On 11/1/2018 6:39 PM, Andrey Repin wrote:
> Greetings, All!
> 
> $ pwd
> /home/anrdaemon/Documents/NIX/CA-tutorial/test
> 
> $ ls -ld bin ca-profile
> lrwxrwxrwx 1 anrdaemon None  61 íîÿ  2 01:15 bin -> /home/anrdaemon/Documents/NIX/CA-tutorial/svn-working/scripts
> -rwx--x--x 1 anrdaemon None 588 äåê 24  2017 ca-profile
> 
> $ cat bin/../ca-profile
> cat: bin/../ca-profile: No such file or directory
> 

Try ls `bin/../`

You'll see a listing of
/home/anrdaemon/Documents/NIX/CA-tutorial/svn-working/.

> $ cat $( realpath -Le "bin/../ca-profile" )
> # @version $Id: ca-profile 82 2014-02-08 05:24:12Z anrdaemon $
> ...
> 
> In simpler words, the bin directory is symlinked from elsewhere.
> realpath -Le resolves correctly, but all other filesystem functions fail.
> 
> I vaguely recall that there was some discussion on the matter, but search
> returns too many results, can't read them all.
> My question, basically: is this expected way of things?

The answer is yes it is expected and works the same on Linux.

> If so, I'd just workaround it. Sad but doable.

Don't be sad just do it. ;p

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple