On 2/19/07, Christian Theune [EMAIL PROTECTED] wrote:
[buildout]
extends = profiles/dev.cfg
and run bin/buildout.
This works very well for us.
It did for me too, but it has now stopped working.
Line 89 in buildout.py says:
data['buildout']['directory'] =
Oups, I forgot that this should go to the distutils list. Please
ignore, I'll repost there.
On 3/16/07, Lennart Regebro [EMAIL PROTECTED] wrote:
On 2/19/07, Christian Theune [EMAIL PROTECTED] wrote:
[buildout]
extends = profiles/dev.cfg
and run bin/buildout.
This works very well for us.
Lennart Regebro wrote:
I'm testing buildout, and one thing I want is to have several cfgs,
one for development, one for staging and one for production. Now,
calling one of the configurations buildout.cfg would make it the
default. That means that if you just run bin/bildout, it will try to
On 2/20/07, Jim Fulton [EMAIL PROTECTED] wrote:
That's not what I want as default behaviour. :-) Can we change this to
complaining that buildout.cfg doesn't exist instead?
Yes. The existing behavior was added primarily to support
bootstrapping, where I still think it makes some sense. Could
I'm testing buildout, and one thing I want is to have several cfgs,
one for development, one for staging and one for production. Now,
calling one of the configurations buildout.cfg would make it the
default. That means that if you just run bin/bildout, it will try to
install that configuration.
Hi,
here's the pattern that we use:
- create a directory 'profiles/' in your buildout
- create a file 'profiles/base.cfg' that describes all parts and their
default configurations
- create a file 'profiles/dev.cfg' that has the development variation
and uses '[buildout] extends=base.cfg'
Then
On 2/19/07, Christian Theune [EMAIL PROTECTED] wrote:
Hi,
here's the pattern that we use:
- create a directory 'profiles/' in your buildout
- create a file 'profiles/base.cfg' that describes all parts and their
default configurations
- create a file 'profiles/dev.cfg' that has the development
