Rev 36: Work around the bugs in updating by nuking the 'trunk' dirs. in

John Arbash Meinel john at
Thu Oct 15 18:36:31 BST 2009


revno: 36
revision-id: john at
parent: john at
committer: John Arbash Meinel <john at>
branch nick: trunk
timestamp: Thu 2009-10-15 12:36:06 -0500
  Work around the bugs in updating by nuking the 'trunk' dirs.
  This will make it harder to 'fake' tags, but hopefully I won't have to do that.
  I wonder if the issue is that the update code is runinng 'bzr update', but these
  branches aren't checkouts, so it *should* be running 'bzr pull'...
  Anyway, the code is currently set up to create shared repositories, so
  this should allow us to re-use everything we have downloaded, and just
  have to rebuild the working tree for each project. A bit of a shame, but
  a small price to pay for updates that actually work.
-------------- next part --------------
=== modified file 'Makefile'
--- a/Makefile	2009-09-25 18:47:02 +0000
+++ b/Makefile	2009-10-15 17:36:06 +0000
@@ -50,7 +50,7 @@
 	cd tools/win32 && $(PYTHON) copytree $(BUILDOUT_FILES) ../../$(BUILD_DIR)
 	$(PYTHON) tools/win32/ makedir $(BUILD_DIR)/inno
 	$(PYTHON) tools/win32/ copytodir tools/win32/bzr.iss.cog $(BUILD_DIR)/inno
-	cd $(BUILD_DIR) && $(PYTHON) remove release */release
+	cd $(BUILD_DIR) && $(PYTHON) remove release */release */trunk
 	cd $(BUILD_DIR) && $(PYTHON)
 	cd $(BUILD_DIR) && bin/buildout
 	cd $(BUILD_DIR) && bin/build-installer.bat $(BZR_TARGET) $(PLUGIN_TARGET)

More information about the bazaar-commits mailing list