Brandon Craig Rhodes wrote:
>> [buildout]
>> ...
>> versions = versions
>
> Should we write something like Grok for buildout, so that it just uses
> sections without having to have them doubly declared up at the top? :-)
Heh, nah, this was a fair cop. I *did* actually know about this, was
just a
Brandon Craig Rhodes wrote:
> Should we write something like Grok for buildout, so that it just uses
> sections without having to have them doubly declared up at the top? :-)
I think it's kind of funny that the Zope project chose XML (a
hierarchical format) for ZCML (which is fairly flat), then c
Philipp von Weitershausen <[EMAIL PROTECTED]> writes:
>> [versions]
>> ZODB3 = 3.8.0
>> ...
>> This didn't work, buildout still tries to install 3.9.0-dev-r77011. Why?!
>
> Because you're not doing it right. You invented a [versions] section but
> you still need to tell buildout to actually use t
Wichert Akkerman wrote:
> You are missing a line here:
>
> versions = versions
Good catch! Seems to be working now...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev
Chris Withers wrote:
> Okay,
>
> So I bumped into the ZODB3 3.9.0-dev-r77011 problem while trying to get
> going with zopeproject.
>
> zopeproject created a buildout.cfg in my test project, so I thought I'd
> lock ZODB to 3.8.0 to prevent problems:
>
> [buildout]
> develop = .
> parts = app te
Previously Chris Withers wrote:
> Okay,
>
> So I bumped into the ZODB3 3.9.0-dev-r77011 problem while trying to get
> going with zopeproject.
>
> zopeproject created a buildout.cfg in my test project, so I thought I'd
> lock ZODB to 3.8.0 to prevent problems:
>
> [buildout]
> develop = .
> par
