[Checkins] SVN: buildout-website/trunk/source/ Removal of some pages of content, for relocation to another site.
Jeff Rush
jrush at taupro.com
Thu Apr 2 04:40:38 EDT 2009
Log message for revision 98788:
Removal of some pages of content, for relocation to another site.
Changed:
U buildout-website/trunk/source/conf.py
D buildout-website/trunk/source/docs/dirstruct.rst
U buildout-website/trunk/source/index.rst
D buildout-website/trunk/source/install.rst
U buildout-website/trunk/source/thanks.rst
-=-
Modified: buildout-website/trunk/source/conf.py
===================================================================
--- buildout-website/trunk/source/conf.py 2009-04-02 06:46:52 UTC (rev 98787)
+++ buildout-website/trunk/source/conf.py 2009-04-02 08:40:38 UTC (rev 98788)
@@ -21,7 +21,6 @@
# Add any Sphinx extension module names here, as strings. They can be extensions
# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
-#JEFF extensions = ['embeddedvideo', 'recipes']
# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']
Deleted: buildout-website/trunk/source/docs/dirstruct.rst
===================================================================
--- buildout-website/trunk/source/docs/dirstruct.rst 2009-04-02 06:46:52 UTC (rev 98787)
+++ buildout-website/trunk/source/docs/dirstruct.rst 2009-04-02 08:40:38 UTC (rev 98788)
@@ -1,140 +0,0 @@
-Directory Structure of a Buildout
-=================================
-
-.. include:: <xhtml1-special.txt>
-
-.. role:: red
-
-.. sidebar:: Layout of a Buildout
-
- .. parsed-literal::
-
- project/
- :red:`bootstrap.py` |dagger|
- :red:`buildout.cfg` |dagger|
- .installed.cfg
- parts/
- develop-eggs/
- bin/
- buildout
- mypython
- eggs/
- downloads/
-
- |dagger| put :red:`red items` under version control
-
-.. rubric:: bootstrap.py
-
-A script to be included with each project to help a new developer set up the
-tree for use with *zc.buildout* after checking out the project. It installs
-from the network the *zc.buildout* and *setuptools* packages into the project
-directory.
-
-The actual URL for fetching the :file:`bootstrap.py` file is:
-
- http://svn.zope.org/\*checkout\*/zc.buildout/trunk/bootstrap/bootstrap.py
-
-
-.. rubric:: buildout.cfg
-
-Contains the default build specification for the entire project but others can
-be defined such as file:`deployment.cfg` and :file:`production.cfg`.
-Specification files can include other specification files.
-
-
-.. rubric:: .installed.cfg
-
-A hidden file that represents the current build state of the project. The
-*zc.buildout* software updates it as parts are installed or removed. The file
-is used by *zc.buildout* to compute the minimum set of changes to bring the
-project into sync with the :file:`buildout.cfg` or other specification file.
-
-
-.. rubric:: parts/
-
-Each part may create a holding directory underneath :file:`parts/` for the
-specific use of the part's recipe. The part directory belongs to the recipe
-responsible for installing/uninstalling the part and is not intended for
-modification by the developer.
-
-
-.. rubric:: develop-eggs/
-
-The directory holds a kind of symlink or shortcut link to the development
-directories elsewhere on the system of distributions being worked on. The
-content of the directory is manipulated by *zc.buildout* in response to
-"develop = DIRS" entries in the build specification file.
-
-
-.. rubric:: bin/
-
-The directory receives executable scripts that *zc.buildout* creates from
-entrypoints defined within eggs and called out in the build specification.
-
-
-.. rubric:: bin/buildout
-
-The command to invoked *zc.buildout* for bringing the state of the project
-directory into sync with a particular build specification.
-
-
-.. rubric:: bin/mypython
-
-Just an example of a specific instance of a Python interpreter that
-encompasses a specific set of parts. The name is arbitrary and there can be
-any number of such custom interpreters.
-
-
-.. rubric:: eggs/
-
-A cache directory of eggs pulled down from the net, ready for mapping onto the
-*sys.path* of specific parts, as given in the build specification. This
-directory may be shared across projects if configured to be in a common
-nnlocation, increasing the speed with which buildouts can be constructed.
-
-
-.. rubric:: downloads/
-
-A cache directory of raw files pulled down from the net, such as compressed
-eggs, zipfiles, etc. After being downloaded into this directory, the contents
-are usually unpacked under a part name under the :file:`parts/`. This
-directory may also be shared across projects, for greater efficiency.
-
-
-.. rubric:: lib/
-
-Not strictly part of *zc.buildout* this directory appears when running within
-a sandbox created by virtualenv. It represents a standard Python lib/
-hierarchy underwhich anything installed is outside the control of
-*zc.buildout*. It generally should be left alone.
-
-.. rubric:: build/
-
-Not strictly part of *zc.buildout* either, it is a scratch directory used by
-distutils/setuptools in the process of constructing eggs.
-
-
-.. rubric:: dist/
-
-Not strictly part of *zc.buildout*, this directory receives the final packed
-representations of distributions such as eggs ready for uploading or sharing.
-
-Example::
-
- $ cd myproject
- $ svn propedit svn:ignore
-
-::
-
- .installed.cfg
- parts
- develop-eggs
- bin
- eggs
- downloads
- lib
- build
- dist
-
-----
-
Modified: buildout-website/trunk/source/index.rst
===================================================================
--- buildout-website/trunk/source/index.rst 2009-04-02 06:46:52 UTC (rev 98787)
+++ buildout-website/trunk/source/index.rst 2009-04-02 08:40:38 UTC (rev 98788)
@@ -5,11 +5,6 @@
screencasts
quotes
- install
- docs/dirstruct
- docs/usecase1_singlemod
- docs/usecase2_wrapmods
- docs/usecase3_wrapckout
docs/index
docs/links
docs/recipe
Deleted: buildout-website/trunk/source/install.rst
===================================================================
--- buildout-website/trunk/source/install.rst 2009-04-02 06:46:52 UTC (rev 98787)
+++ buildout-website/trunk/source/install.rst 2009-04-02 08:40:38 UTC (rev 98788)
@@ -1,93 +0,0 @@
-Overview of the Installation Process
-====================================
-
-The `zc.buildout`_ software is very easy to install with only one dependency,
-on the *setuptools* package that provides manipulation facilities for Python
-eggs.
-
-1. Many **existing projects** are already based on *zc.buildout* and include
- within their project files the necessary :file:`bootstrap.py` file. To
- activate use of *zc.buildout* within such a project, simply run that
- :file:`bootstrap.py` using the specific Python interpreter for the project.
- This may be the system Python or in the case of a `virtualenv`_ sandbox,
- the Python within the :file:`bin/` subdirectory of the project.
-
- ::
-
- $ cd projectdir
- $ bin/python bootstrap.py
-
-.. sidebar:: Don't have an ``easy_install`` command?
-
- The :program:`easy_install` command comes as part of the `setuptools`_
- package. To install it, download the :file:`ez_setup.py` file into a
- temporary directory and run it with Administrator privileges.
-
-2. While *zc.buildout* is most often installed within each project directory,
- it can also be **installed system-wide**, to make it easy to create new
- projects.
-
- ::
-
- $ easy_install zc.buildout
-
- This gives you a new command named :program:`buildout` to use in
- initializing or updating a project.
-
-.. sidebar:: For an even more isolated build environment...
-
- To use an isolated instance of Python within the project, the following
- commands will create a new sandbox and establish use of *zc.buildout*
- within it.
-
- ::
-
- $ virtualenv --no-site-packages newproject
- $ cd newproject
- $ bin/easy_install zc.buildout
- $ bin/buildout init
-
-3. To **add zc.buildout to a new project**, the primary step is to execute the
- :program:`buildout init` command while your current directory is set to the
- root of the project directory. This command will create all necessary
- files/directories, including a minimal :file:`buildout.cfg` file to control
- buildout.
-
- ::
-
- $ cd newproject
- $ buildout init
-
- This command sequence will use the system Python for the project. If you
- have some other project set up that uses *zc.buildout* you can borrow its
- :program:`buildout` command to initialize your new project.
-
- ::
-
- $ cd newproject
- $ /oldproject/bin/buildout init
-
- Unfortunately this sequence of commands will not provide a
- :file:`bootstrap.py` command for others to use to initialize *zc.buildout*
- when they receive a copy of your project. Therefore it is recommended that
- you download and **incorporate a copy of** :file:`bootstrap.py` **within your
- project fileset**.
-
- ::
-
- $ cd newproject
- $ wget http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py
-
-----
-
-A good next step in understanding *zc.buildout* is :doc:`docs/dirstruct` which
-also covers which file/directories should be under version control and which
-should not.
-
-
-.. _`ez_setup.py`: http://peak.telecommunity.com/dist/ez_setup.py
-.. _`bootstrap.py`: http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py
-.. _`zc.buildout`: http://pypi.python.org/pypi/zc.buildout
-.. _`virtualenv`: http://pypi.python.org/pypi/virtualenv
-.. _`setuptools`: http://peak.telecommunity.com/DevCenter/setuptools
-
Modified: buildout-website/trunk/source/thanks.rst
===================================================================
--- buildout-website/trunk/source/thanks.rst 2009-04-02 06:46:52 UTC (rev 98787)
+++ buildout-website/trunk/source/thanks.rst 2009-04-02 08:40:38 UTC (rev 98788)
@@ -11,7 +11,6 @@
here):
- Baiju M
- - Jeff Rush
- Marius Gedminas
- Martijn Faassen
- Paul Carduner
More information about the Checkins
mailing list