Hi Jim. Thank you for your reply. I use a number of separate config
files for buildouts, some with longer paths - was hoping to shorten them
up a bit to make them clearer (particularly if they originate from same
root).
One other thing that I have not yet seen is using the part name within
the part which would be useful. Something like:
[foobar]
baz = bar
log = /some/path/${foobar:?}-${foobar:baz}.log
Many thanks.
Regards,
David
Jim Fulton wrote:
On Feb 14, 2008, at 2:58 PM, David Pratt wrote:
Hi. I have done some fairly sophisticated buildouts over the past year
but here's something I have not done with an extension before now that
I thought ought to be possible:
[buildout]
extends = ${some-part:path}/foo/bar.cfg
[some-part]
path = /some/where/on/my/filesystem
This produces an error while initializing since it is unable to find
the file but works correctly if the full path is provided. I use
substitutions like this all over the place. Should they not work in
the buildout part as well? Many thanks.
Substitutions don't work for extends because extension (assembling files
to create a configuration database) happens before substitutions.
Jim
--
Jim Fulton
Zope Corporation
_______________________________________________
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
