[Checkins] SVN: zc.buildout/trunk/ - Of course, it only makes sense to run this test if os.symlink exists.

[Sidnei da Silva]

Log message for revision 89803:
  
  - Of course, it only makes sense to run this test if os.symlink exists.
    Also, add an entry to CHANGES.txt
  

Changed:
  U   zc.buildout/trunk/CHANGES.txt
  U   zc.buildout/trunk/src/zc/buildout/tests.py

-=-
Modified: zc.buildout/trunk/CHANGES.txt
===================================================================
--- zc.buildout/trunk/CHANGES.txt	2008-08-13 17:18:36 UTC (rev 89802)
+++ zc.buildout/trunk/CHANGES.txt	2008-08-13 17:23:40 UTC (rev 89803)
@@ -4,6 +4,12 @@
 Change History
 **************
 
+1.1.2 (Unreleased)
+==================
+
+- Fixed a bug that would cause buildout to break while computing a
+  directory hash if it found a broken symlink (Launchpad #250573)
+
 1.1.1 (2008-07-28)
 ==================
 

Modified: zc.buildout/trunk/src/zc/buildout/tests.py
===================================================================
--- zc.buildout/trunk/src/zc/buildout/tests.py	2008-08-13 17:18:36 UTC (rev 89802)
+++ zc.buildout/trunk/src/zc/buildout/tests.py	2008-08-13 17:23:40 UTC (rev 89803)
@@ -1108,9 +1108,9 @@
 
     """
 
-def bug_250537_broken_symlink_doesnt_affect_sig():
-    """
-    
+if hasattr(os, 'symlink'):
+    def bug_250537_broken_symlink_doesnt_affect_sig():
+        """
 If we have a develop recipe, it's signature shouldn't be affected by
 broken symlinks, and better yet, computing the hash should not break
 because of the missing target file.