[Checkins] SVN: bluebream/website/docs/v1.0/gettingstarted.rst update the doc for the python_package paster variable

[Christophe Combelles]

Log message for revision 111029:
  update the doc for the python_package paster variable
  

Changed:
  U   bluebream/website/docs/v1.0/gettingstarted.rst

-=-
Modified: bluebream/website/docs/v1.0/gettingstarted.rst
===================================================================
--- bluebream/website/docs/v1.0/gettingstarted.rst	2010-04-18 00:43:38 UTC (rev 111028)
+++ bluebream/website/docs/v1.0/gettingstarted.rst	2010-04-18 22:38:16 UTC (rev 111029)
@@ -162,6 +162,9 @@
 are already passed through command line. Other variables can also be
 given values from the command line, if required:
 
+- ``python_package`` -- Name of the main Python package (possibly with
+  namespaces)
+
 - ``interpreter`` -- Name of the custom Python interpreter
 
 - ``version`` -- Version (like 0.1)
@@ -258,10 +261,10 @@
 
 .. image:: images/gettingstarted4.png
 
-The second (mmh no, first!) most common thing that should be run are the unit
-tests.  BlueBream creates a testrunner using the ``zc.recipe.testrunner``
-Buildout recipe.  User can see a ``test`` command inside the ``bin`` directory.
-To run the test cases, the following command is used::
+The second most common thing that should be run are the unit tests.  BlueBream
+creates a testrunner using the ``zc.recipe.testrunner`` Buildout recipe. The user
+can see a ``test`` command inside the ``bin`` directory.  To run the test cases,
+the following command is used::
 
   $ ./bin/test
 
@@ -329,6 +332,7 @@
     |       `-- README.txt
     `-- versions.cfg
 
+
 The name of the top-level directory will always be the project name as given in
 the wizard.  The name of the egg will also be the same as the package name by
 default. The user can change it to something else from ``setup.py``.  Here are