1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
[buildout]
software_home = ${:directory}
extensions +=
buildout.dumppickedversions
extends =
../profiles/versions.cfg
../profiles/software-definition.cfg
../software-profiles/apache.cfg
../software-profiles/automake-1.9.cfg
../software-profiles/erp5.cfg
../software-profiles/garbage-collector.cfg
../software-profiles/tokyocabinet.cfg
../software-profiles/flare.cfg
../software-profiles/haproxy.cfg
../software-profiles/imagemagick.cfg
../software-profiles/libevent.cfg
../software-profiles/libtool.cfg
../software-profiles/memcached.cfg
../software-profiles/mysql-tritonn-5.0.cfg
../software-profiles/ocropus.cfg
../software-profiles/oood.cfg
../software-profiles/openoffice-bin.cfg
../software-profiles/python-2.4.cfg
../software-profiles/rdiff-backup.cfg
../software-profiles/w3m.cfg
../software-profiles/varnish.cfg
../software-profiles/zope-2.8.cfg
../profiles/common.cfg
python = python2.4
versions = versions
parts =
eggs
apache
memcached
rdiff-backup
ocropus
haproxy
varnish
flare
w3m
imagemagick
mysql-tritonn-5.0
zope-2.8
cmf15
itools
pythonbin2.4
bootstrap2.4
mysql-python
products-deps
products-erp5
products-erp5-development
products-other
openoffice-bin
oood
[show-requirements]
recipe = plone.recipe.command
command =
echo "Required binary files: ${requirements:binary}"
echo "Required header files: ${requirements:development}"
update-command = ${:command}
[software_definition]
software_home = ${buildout:software_home}
# as mysql-python part, which uses mysql-python-env is not depending directly
# on mysql-tritonn-5.0 part, but official buildout shall provide whole software
# set dependency here
# Thanks to this it is possible to build mysql-python part in own environment
# with local mysql, but by default buildout mysql will be used.
mysql_software = ${mysql-tritonn-5.0:location}