-* .gitignore: no need to explain
-* README.txt: self-explained
* bootstrap.py: a copy of the zc.buildout bootstrap script, as provided at
`zc.buildout code repository`_
* buildout.cfg: a buildout configuration file where:
develop-eggs-directory = lib/buildout/develop-eggs
s-directory = lib/buildout/downloads
+ download- = lib/buildout/downloads
eggs-directory = lib/buildout/eggs
installed = lib/buildout/.installed.cfg
parts-directory = lib/buildout/parts
git clone https://github.com/benoitbryon/python-buildout-directories.git
+ # In this example, we need to prepare some directories.
+ mkdir -p lib/buildout/downloads
# Bootstrap zc.buildout, i.e. install it.
python bootstrap.py --distribute
- * lib/buildout/ (you created this as an empty directory)
+ * lib/buildout/downloads/
Non standard "mkdir -p lib/buildout"
+ A similar thing happens with lib/buildout/downloads, but it is a bit special.
+ See `download-cache`_ below.
One thing has been added to a classic buildout workflow: the
"mkdir -p lib/buildout" command.
If your project is not only about Python and buildout, you may put other
things in lib. In some projects, I saw some PHP libraries in lib/.
+In the example above, we setup a download cache in local
+"lib/buildout/downloads". This may not be the most efficient configuration. I
+mean "download-cache" directory is typically a shared folder, such as
+"~/.buildout-cache". Anyway, buildout doesn't automatically create it and
+complains if it doesn't exist.
Reusing directories configuration