Housekeeper should not fail when skia-autogen is reset

tools/update-doxygen.sh

Index: tools/update-doxygen.sh
===================================================================
--- tools/update-doxygen.sh	(revision 8926)
+++ tools/update-doxygen.sh	(working copy)
@@ -13,6 +13,16 @@
 #  export DOXYGEN_COMMIT=false
 #  bash update-doxygen.sh
 
+function check_out_docs {
+  svn checkout https://skia-autogen.googlecode.com/svn/docs  # writeable
+  ret_code=$?
+  if [ $ret_code != 0 ]; then
+    # docs directory does not exist, skia-autogen must have been reset.
+    # Create a non svn docs directory instead.
+    mkdir docs

[borenet, 2013/05/01 12:10:39]

Should you "svn add" docs here?  I would think that the "svn status" on line 68
will fail since docs is not yet a working copy.

[rmistry, 2013/05/01 12:15:22]

Yes svn status will fail since its not yet a working copy but thats ok because
the changes are actually submitted by merge_into_svn.py, I did not want to break
backwards compatibility of this file if it is used other than the housekeeper.

svn add here will not work as well because the parent directory is not a working
copy.

+  fi
+}
+
 # Prepare a temporary dir and check out Skia trunk and docs.
 cd
 DOXYGEN_TEMPDIR=${DOXYGEN_TEMPDIR:-/tmp/skia-doxygen}
@@ -28,12 +38,20 @@
 fi
 if [ -d "docs" ]; then
   svn update --accept theirs-full docs
+  svn info docs
+  ret_code=$?
+  if [ $ret_code != 0 ]; then
+    # This is not a valid SVN checkout.
+    rm -rf docs
+    check_out_docs
+  fi
 else
-  svn checkout https://skia-autogen.googlecode.com/svn/docs  # writeable
+  check_out_docs
+fi
+
 if [ ! -f "docs/static_footer.txt" ]; then
   cp trunk/tools/doxygen_footer.txt docs/static_footer.txt
 fi
-fi
 
 # Run Doxygen.
 cd trunk