| 1 |
- global build requirement checker
|
| 2 |
- needs recipe
|
| 3 |
- needs per profile dependency declaration
|
| 4 |
- implement declared parts (*/buildout.cfg empty)
|
| 5 |
- merge from:
|
| 6 |
- https://svn.erp5.org/repos/public/experimental/erp5.buildout-zope-2.12/
|
| 7 |
- use more of buildout automatic dependency resolution
|
| 8 |
- software-profiles/openoffice-bin.cfg:
|
| 9 |
- consider using own recipe or zorg.recipe.openoffice, which would be
|
| 10 |
closer to buildout usage (internal cache, etc)
|
| 11 |
- add bin/ and var/bin/ to path
|
| 12 |
- if software do not provide instance, put its binaries to bin/
|
| 13 |
- use declarative way of selecting in-buildout dependencies
|
| 14 |
For example mysql-python egg is build against locally built mysql, but
|
| 15 |
version of mysql is hardcoded in mysql-python egg part.
|
| 16 |
- have all eggs available as software, but use them selectively in instances
|
| 17 |
- convert all ERP5 products into eggs, but allow in development profile to
|
| 18 |
have them locally editable and commitable (develop)
|
| 19 |
- binaries generated by software buildout shall have precedence in PATH in
|
| 20 |
software *and* instance buildouts
|
| 21 |
- make eggs defined with standalone instance recipe inside instance instead
|
| 22 |
of globally for buildout
|
| 23 |
- update software-profiles/apache.cfg to build fully modular apache (with ssl,
|
| 24 |
cache, etc) which will give full control while creating apache instances
|
| 25 |
- check if all profiles are working in networked way - that no checkout of
|
| 26 |
buildout structure is required, so it is possible to use extend over the
|
| 27 |
network
|
Parent Directory
| 
Revision Log