[Checkins] SVN: zc.buildout/trunk/zc.recipe.egg_/ Removed (documentation of) the unzip option. It seems to be too

[Jim Fulton]

Log message for revision 69374:
  Removed (documentation of) the unzip option.  It seems to be too
  brittle and failed tests with the latest setuptools.
  

Changed:
  U   zc.buildout/trunk/zc.recipe.egg_/README.txt
  U   zc.buildout/trunk/zc.recipe.egg_/src/zc/recipe/egg/README.txt
  U   zc.buildout/trunk/zc.recipe.egg_/src/zc/recipe/egg/api.txt

-=-
Modified: zc.buildout/trunk/zc.recipe.egg_/README.txt
===================================================================
--- zc.buildout/trunk/zc.recipe.egg_/README.txt	2006-08-08 11:46:36 UTC (rev 69373)
+++ zc.buildout/trunk/zc.recipe.egg_/README.txt	2006-08-08 15:14:26 UTC (rev 69374)
@@ -26,12 +26,6 @@
 python
     The name of a section defining the Python executable to use.
     This defaults to buildout.
-    
-unzip
-   The value of this option must be either true or false. If the value
-   is true, then the installed egg will be unzipped. Note that this is
-   only effective when an egg is installed.  If a zipped egg already 
-   exists in the eggs directory, it will not be unzipped.
 
 scripts
    Control which scripts are generated.  The value should be a list of

Modified: zc.buildout/trunk/zc.recipe.egg_/src/zc/recipe/egg/README.txt
===================================================================
--- zc.buildout/trunk/zc.recipe.egg_/src/zc/recipe/egg/README.txt	2006-08-08 11:46:36 UTC (rev 69373)
+++ zc.buildout/trunk/zc.recipe.egg_/src/zc/recipe/egg/README.txt	2006-08-08 15:14:26 UTC (rev 69374)
@@ -29,12 +29,6 @@
    Python executable is found in the executable option of the named
    section. 
 
-unzip
-   The value of this option must be either true or false. If the value
-   is true, then the installed egg will be unzipped. Note that this is
-   only effective when an egg is installed.  If a zipped egg already 
-   exists in the eggs directory, it will not be unzipped.
-
 scripts
    Control which scripts are generated.  The value should be a list of
    zero or more tokens.  Each token is either a name, or a name
@@ -141,20 +135,16 @@
     ... recipe = zc.recipe.egg
     ... find-links = %(server)s
     ... index = %(server)s/index
-    ... unzip = true
     ... """ % dict(server=link_server))
 
-We also used the unzip uption to request a directory, rather than
-a zip file.
-
     >>> print system(buildout),
 
 Then we'll get a new demo egg:
 
     >>> ls(sample_buildout, 'eggs')
     -  demo-0.2-py2.3.egg
-    d  demo-0.3-py2.3.egg
-    d  demoneeded-1.0-py2.3.egg
+    -  demo-0.3-py2.3.egg
+    -  demoneeded-1.0-py2.3.egg
 
 Note that we removed the eggs option, and the eggs
 defaulted to the part name.

Modified: zc.buildout/trunk/zc.recipe.egg_/src/zc/recipe/egg/api.txt
===================================================================
--- zc.buildout/trunk/zc.recipe.egg_/src/zc/recipe/egg/api.txt	2006-08-08 11:46:36 UTC (rev 69373)
+++ zc.buildout/trunk/zc.recipe.egg_/src/zc/recipe/egg/api.txt	2006-08-08 15:14:26 UTC (rev 69374)
@@ -6,7 +6,7 @@
 recipe provides an API that other recipes can use.
 
 A recipe can reuse the egg recipe, supporting the eggs, find-links,
-index, python, and unzip options.  This is done by creating an egg
+index, and pythonoptions.  This is done by creating an egg
 recipe instance in a recipes's contructor.  In the recipe's install
 script, the egg-recipe instance's working_set method to collect the
 requested eggs and working set.