[Checkins] SVN: zc.buildout/trunk/ Reverted to last known good
state. The factoring was too hard. :)
Jim Fulton
jim at zope.com
Tue Aug 29 16:48:22 EDT 2006
Log message for revision 69879:
Reverted to last known good state. The factoring was too hard. :)
It would have broken old bootstrap scripts. Now my problem is that if
I update buildout in a way that recipes depend on, people will have to
update their buildouts by running the bootstrap script. This isn't ideal.
Changed:
U zc.buildout/trunk/buildout.cfg
U zc.buildout/trunk/todo.txt
D zc.buildout/trunk/zc.buildoutsupport/
-=-
Modified: zc.buildout/trunk/buildout.cfg
===================================================================
--- zc.buildout/trunk/buildout.cfg 2006-08-29 18:41:08 UTC (rev 69878)
+++ zc.buildout/trunk/buildout.cfg 2006-08-29 20:48:22 UTC (rev 69879)
@@ -1,5 +1,5 @@
[buildout]
-develop = zc.recipe.egg_ zc.recipe.testrunner zc.buildoutsupport
+develop = zc.recipe.egg_ zc.recipe.testrunner
parts = test
# prevent slow access to cheeseshop:
Modified: zc.buildout/trunk/todo.txt
===================================================================
--- zc.buildout/trunk/todo.txt 2006-08-29 18:41:08 UTC (rev 69878)
+++ zc.buildout/trunk/todo.txt 2006-08-29 20:48:22 UTC (rev 69879)
@@ -1,4 +1,13 @@
+- Need a better way to handle buildout updates. If I update buildout
+ and new versions of recipes depend on that, people will have to use
+ the bootstrap script to get a newer version of buildout or the
+ recipes won't load correctly.
+
+ I either need a more clever recipe loader that can load older
+ recipes when newer recipes aren't compatible with the existing
+ buildout version, or I need to make the buildout self updating.
+
- Use setuptools PackageIndex objects to improve performance by
deciding whether we need to download anything without using
easy_install.
More information about the Checkins
mailing list