<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 2/4/09 4:03 PM, Uli Fouquet wrote:
<blockquote cite="mid:1233759827.6908.25.camel@pu" type="cite">
<pre wrap="">Hi there,
Wichert Akkerman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Previously Uli Fouquet wrote:
</pre>
</blockquote>
<pre wrap=""><!---->
[snip]
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">This looks like a serious issue to me. Many of the configuration files
in etc/ contain hardcoded paths and it looks difficult to (re)generate
them using existing buildout-recipes (which would be the first solution
I would think of).
</pre>
</blockquote>
<pre wrap="">collective.recipe.template is meant to help with situations like this.
I use it for exactly this problem.
</pre>
</blockquote>
<pre wrap=""><!---->
Great :-) That really looks like what we need. Thanks, Wichert!
Just two things: could you imagine support for passing the content via
in-file text like this or similar::
[buildout]
...
[sitezcml]
recipe = collective.recipe.template
content = <configure />
output = /etc/site.zcml
</pre>
</blockquote>
<br>
I can imagine it, but personally I find that just makes buildout.cfg
very hard to read, and you loose syntax checking and highlighting
features from your editor, so I have no intention to implement this
myself.<br>
<br>
<blockquote cite="mid:1233759827.6908.25.camel@pu" type="cite">
<pre wrap="">And the other thing: did you ever experience trouble with Windows based
environments? I ask only because of the `stat.S_IMODE` calls in the
recipe and to be sure.
</pre>
</blockquote>
<br>
I haven't tested, but I haven't received any bugreports either. Test
feedback would be welcome :)<br>
<br>
Wichert.<br>
<br>
</body>
</html>