ln -f doesn't replace a symlink to a directory, it simply tries to create

a symlink of the same name inside the directory, which is impossible on the
Chrome OS read-only filesystem

Review URL: http://codereview.chromium.org/7628007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96514 0039d316-1c4b-4281-b951-d872f2087c98

chrome/test/chromeos/autotest/files/client/deps/pyauto_dep/setup_test_links.sh

@@ -8,8 +8,10 @@
 
 ln -f -s /opt/google/chrome/chrome $(dirname $0)/chrome
 ln -f -s /opt/google/chrome/chrome.pak $(dirname $0)/chrome.pak
-ln -f -s /opt/google/chrome/locales $(dirname $0)/locales
-ln -f -s /opt/google/chrome/resources $(dirname $0)/resources
+[ -L $(dirname $0)/locales ] || ln -f -s /opt/google/chrome/locales \
+    $(dirname $0)/locales
+[ -L $(dirname $0)/resources ] || ln -f -s /opt/google/chrome/resources \
+    $(dirname $0)/resources
 ln -f -s /opt/google/chrome/resources.pak $(dirname $0)/resources.pak
 
 mkdir -p $(dirname $0)/chromeos