- as mysql-python egg build is software component, no instance component, it

   is ok - and even required - to use in-buildout definition of component, as
   it triggers buildout dependency


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32771 20353a03-c40f-0410-a6d1-a30d3c3de9de

buildout/TODO.txt

@@ -23,3 +23,6 @@
    - consider using own recipie
  - add bin/ and var/bin/ to path
  - if software do not provide instance, put its binaries to bin/
+ - use declarative way of selecting in-buildout dependencies
+     For example mysql-python egg is build against locally built mysql, but
+     version of mysql is hardcoded in mysql-python egg part.

buildout/software-profiles/erp5.cfg

@@ -35,7 +35,7 @@ egg = itools
 include-dirs = /usr/include/glib-2.0:/usr/lib/glib-2.0/include/:/usr/lib64/glib-2.0/include/
 
 [mysql-python-env]
-PATH =${software_definition:mysql_software}/bin:%(PATH)s
+PATH =${mysql-tritonn-5.0:location}/bin:%(PATH)s
 
 [mysql-python]
 recipe = zc.recipe.egg:custom