[Mono-bugs] [Bug 78580][Nor] Changed - UnixSymbolicLinkInfo.Content fails with relative symlink

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by jonpryor at vt.edu.

http://bugzilla.ximian.com/show_bug.cgi?id=78580

--- shadow/78580	2006-07-02 15:25:53.000000000 -0400
+++ shadow/78580.tmp.9973	2006-07-02 15:38:45.000000000 -0400
@@ -91,6 +91,24 @@
 I'll look into fixing this.
 
 ------- Additional Comments From jonpryor at vt.edu  2006-07-02 15:25 -------
 I didn't get the exception apparently because I was in a directory
 named `tmp'.  Go figure.  It fails in the same why if I execute in
 another directory.
+
+------- Additional Comments From jonpryor at vt.edu  2006-07-02 15:38 -------
+I've goot good news and bad news:
+
+The good news: it doesn't generate an exception if you use HEAD.
+
+The bad news: HEAD still doesn't generate the correct output:
+
+infoLA has contents: True
+infoLA contents full name: /tmp/tmp/a
+infoLB has contents: True
+infoLB contents full name: /tmp/la/b
+
+Notice that the 2nd line is wrong.  This is due to a bug in UnixPath,
+in which UnixPath.Combine ("/a", "/b") returns "/a/b" instead of "/b"
+(which is what System.IO.Path.Combine would do).
+
+Do you need a fix for the 1.1.13 branch?  Or can you migrate to HEAD?