This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [ANNOUNCEMENT]: Important change to symbolic link functionality


On Thu, Feb 22, 2001 at 03:26:05PM +0300, Egor Duda wrote:
> try this:
> 
> ==================================
> cd /tmp
> mkdir -p symlink_test/1
> mkdir -p symlink_test/2
> touch symlink_test/1/1.fil
> touch symlink_test/2/2.fil
> cd symlink_test
> ln -s 1 t1
> ln -s ../2 t1/new_2
> cd /tmp
> mv symlink_test ~/
> cd ~/symlink_test/t1/new_2
> ls
> ==================================
> ls should show 2.fil
> 
> now open <your_home_dir>/symlink_test/1/ with explorer and oops, new_2
> isn't shortcut anymore.

You're right. This error is reproducable in Cygwin and U/WIN.

However, I have just changed Cygwin to do it right ;-)

The problem is that a shortcut has to contain a DOS path, obviously.
The new strategy is as follows:

- If the target path is an absolute path save the absolute DOS path.

- If the target doesn't exist save a relative DOS path (who cares?).

- If the target path is accessible as relative DOS path save that relative
  DOS path.

- If both of above fails save the absolute path.

At least your above given example now works.
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]