<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns="http://usefulinc.com/ns/doap#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><Project><name>collective.recipe.template</name>
<shortdesc>Buildout recipe to generate a text file from a template</shortdesc>
<description>Introduction
============

This recipe can be used to generate textfiles from a (text) template.

A short example::

  [buildout]
  parts = zope.conf

  [message]
  recipe = collective.recipe.template
  input = templates/message.in
  output = /message

  mymessage = Hello, World!


In the template you can use the exact same variables as you can use
in the buildout configuration. For example an input file can look like this::

  My top level directory is ${buildout:directory}
  Executables are stored in ${buildout:bin-directory}


As an extension to the buildout syntax you can reference variables from
the current buildout part directly. For example::

  My message is: ${mymessage}


Why another template recipe?
----------------------------

Both `iw.recipe.template`_ and `inquant.recipe.textfile`_ claim to do the
same thing. I have found them to be undocumented and too buggy for real
world use, and neither are in a public repository where I could fix them. In
addition this implementation leverages the buildout variable substitution
code, making it a lot simpler.




Changelog
=========

1.0rc2 - 2008-07-04
-------------------

* Add a MANIFEST.in with instructions to include docs/, otherwise the package
  will not install.
  [wichert]


1.0rc1 - 2008-07-04
-------------------

* Initial release.
  [wichert]</description>
<maintainer><foaf:Person><foaf:name>Wichert Akkerman</foaf:name>
<foaf:mbox_sha1sum>b63a6afc1b6baf3563100e9a42e7f274c0f8bdc2</foaf:mbox_sha1sum></foaf:Person></maintainer>
<release><Version><revision>1.0rc2</revision></Version></release>
</Project></rdf:RDF>