[Checkins] SVN: zc.buildout/trunk/ Added ignores for various computed files.

Jim Fulton jim at zope.com
Wed Jun 7 18:52:39 EDT 2006


Log message for revision 68518:
  Added ignores for various computed files.
  

Changed:
  _U  zc.buildout/trunk/
  _U  zc.buildout/trunk/eggrecipe/src/
  _U  zc.buildout/trunk/src/
  _U  zc.buildout/trunk/testrunnerrecipe/src/
  U   zc.buildout/trunk/todo.txt

-=-

Property changes on: zc.buildout/trunk
___________________________________________________________________
Name: svn:ignore
   + eggs
parts
.installed.cfg
bin



Property changes on: zc.buildout/trunk/eggrecipe/src
___________________________________________________________________
Name: svn:ignore
   + zc.recipe.egg.egg-info



Property changes on: zc.buildout/trunk/src
___________________________________________________________________
Name: svn:ignore
   + zc.buildout.egg-info



Property changes on: zc.buildout/trunk/testrunnerrecipe/src
___________________________________________________________________
Name: svn:ignore
   + zc.recipe.testrunner.egg-info


Modified: zc.buildout/trunk/todo.txt
===================================================================
--- zc.buildout/trunk/todo.txt	2006-06-07 22:45:45 UTC (rev 68517)
+++ zc.buildout/trunk/todo.txt	2006-06-07 22:52:39 UTC (rev 68518)
@@ -38,3 +38,20 @@
 
 - Logging
 
+Issue:
+
+- If recipes require zc.buildout, there are weird problems for the
+  tests, because we'll try to get zc.buildout when the test runs the
+  recipe and there might not be a convenient way for it to do that.
+
+  This is really a case of "plugins".  A plugin system has to be
+  prepared to dynamically find eggs of the thing doing the plugging.
+  This is a potential problem for my plan of just including eggs (or
+  link dests) in generated script paths, as that would prevent a
+  plugin system from finding the eggs already loaded.  We really need
+  to include the egg dirs as well.  This feels a bit weird.
+
+  Suppose you have some package, X and X supports plugins.  If X loads
+  a plugin and the plugin requires X, then we need to be able to find
+  X's egg.  Furthermore, if we upgrade the plugin when we find it, we
+  will end up upgrading X, which makes no sense.  



More information about the Checkins mailing list