[Zope3-dev] Buildout default behaviour

[Jim Fulton]

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
> install that configuration. That's fine for installing, but not for
> updating. If you install it with -c staging.cfg, and then without -c
> at all, it will try to switch to the buildut.cfg configuration, which
> is not what you want.
> 
> Now, a clever way around this ought to be to have no buildout.cfg at
> all, and therefore no default, right? Nope, because if you run it
> then, it will create an empty buildout.cfg, and then promptly go
> around building it. Which has the effect that everything gets
> UNINSTALLED!
> 
> 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 you report
this as a bug on:

   https://bugs.launchpad.net/zc.buildout/+bugs

Also, in the future, I'd prefer that general buildout questions be
raised on the distutils-sig mailing list,

   http://mail.python.org/mailman/listinfo/distutils-sig

(Questions about zope3-specific recipes would be best asked here.)

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org