diff options
| author | tarek <none@none> | 2009-09-26 20:12:50 +0200 |
|---|---|---|
| committer | tarek <none@none> | 2009-09-26 20:12:50 +0200 |
| commit | 775967de5b20d48a50f2ca050a87d8fa4890170d (patch) | |
| tree | 0f43763697d9385fbb1f84f07cd12c96b8d409c1 /README.txt | |
| parent | 2f2ef4a897642dda08a95e4544d05b4012850dcd (diff) | |
| download | external_python_setuptools-775967de5b20d48a50f2ca050a87d8fa4890170d.tar.gz external_python_setuptools-775967de5b20d48a50f2ca050a87d8fa4890170d.tar.bz2 external_python_setuptools-775967de5b20d48a50f2ca050a87d8fa4890170d.zip | |
this is not finished yet. lets make a clean work for 0.6.3 for zc.buildout support
--HG--
branch : distribute
extra : rebase_source : 39abb9d72dc676082ce0337453efe20884936dd5
Diffstat (limited to 'README.txt')
| -rwxr-xr-x | README.txt | 13 |
1 files changed, 5 insertions, 8 deletions
@@ -162,15 +162,12 @@ Install FAQ - **How does Distribute interact with zc.buildout?** Some work is being done on zc.buildout side to make its bootstrap - work with Distribute. Until then, using Distribute in zc.buildout is a bit - tricky. + work with Distribute. Until then, using Distribute in zc.buildout is a bit + tricky because the bootstrap process of zc.buildout hardcodes the + installation of Setuptools. - Like virtualenv, Distribute has to be installed after setuptools. The simplest - way is to add it in a ``zc.recipe.egg`` section so the job is done when you - build your buildout. - - If you are combining zc.buildout and virtualenv, you might fail in the - problem described in the previous FAQ entry. + The plan is to come with a working bootstrap.py for zc.buildout for the + 0.6.3 release. ----------------------------- Feedback and getting involved |