- in reality development profile is like deployment, but with starting supervisor and using local software home


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

Put software and instance profiles in grouped directories.
Cleanup official.cfg extends.


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

This is bad way[tm] of solving this, but in long run this shall be part of
supervisord.


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

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

 - fix typo


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

 - rename templates and output files to be consistent with original (mysqld -> mysqld_safe)
 - reuse buildout automatic dependency
 - put binaries into var/bin and reuse from there

Sometimes software is in "data" directory - especially those binaries which
are controlling software configuration.


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

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

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

 - create common directories globally


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

Access to this file from buildout level will allow to reuse configuration easily


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

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

 - create initial my.cnf template


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

If there is no change, there is no need to recreate mysql data files


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

Because of side effect of many different recipe such directory might exists,
but as isn't sure it is better to try-create it.


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

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

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

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

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

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

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

 - reuse buildout possibility to use local variable


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

 - reorganise and cleanup namespaces


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

 - group client and server options and reuse it in script generation


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

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

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

We can use supervisor globally in buildout by providing hooks from instance
profiles.


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

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

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

development.cfg:
 - define mysql_datadir for development profile
official.cfg:
 - globally define used mysql software component in official profile
mysql-tritonn-5.0-instance/buildout.cfg:
 - fix copy and paste issue with mysql_install_db
 - use profile configuration to access files produced by software component
 - made options less verbose

mysql-tritonn-5.0-instance/templates/mysqladmin.in:
mysql-tritonn-5.0-instance/templates/mysql.in:
 - use profile configuration to choose software component


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

This is very disliked end-of-day-commit. Even worse - this is mostly copy & paste
from original. Work in progress.


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