Buildout configurations in a subdirectory stopped working.
On 2/19/07, Christian Theune <ct@gocept.com> 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'] = os.path.dirname(config_file) This must be a recent change (< 2 weeks) because this makes buildout fail if you have the cfg files anywhere else than root. I'd like to know the rationale for this change, as I'd like to be able to have the profiles in a subdirectory. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
On Mar 16, 2007, at 5:23 AM, Lennart Regebro wrote:
On 2/19/07, Christian Theune <ct@gocept.com> 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.
I don't know what "it" is. I have no problem extending a configuration file in a subdirectory. In fact, i tried the example above (as much as is shown) without difficulty.
Line 89 in buildout.py says:
data['buildout']['directory'] = os.path.dirname (config_file)
This must be a recent change (< 2 weeks)
No. Buildout has always set the default buildout directory to the directory containing the configuration file given on the command line or to the current working directory. BTW, svn blame shows that that line was last modified on Dec 7.
because this makes buildout fail if you have the cfg files anywhere else than root.
I can't reproduce this. Can you construct a minimal example that illustrates this? Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
On 3/17/07, Jim Fulton <jim@zope.com> wrote:
I don't know what "it" is. I have no problem extending a configuration file in a subdirectory. In fact, i tried the example above (as much as is shown) without difficulty.
Extending is no problem, it's using thats the problem. :-)
No. Buildout has always set the default buildout directory to the directory containing the configuration file given on the command line or to the current working directory.
BTW, svn blame shows that that line was last modified on Dec 7.
Thats very weird, since just two weeks ago I was able to have configuration files in a subdirectory and have the buildout directory be the well, buildout directory... One difference was that I first had the configuration file in the root, and then moved them. This time I checked it all out from scratch...
I can't reproduce this. Can you construct a minimal example that illustrates this?
OK, I'll try. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
participants (2)
-
Jim Fulton -
Lennart Regebro