forked from tseaver/compoze
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fleshed out Sphinx documentation skelington.
git-svn-id: svn+ssh://svn.repoze.org/svn/compoze/trunk@8601 8f1d8bf8-68d2-4fbe-a113-2afb08c80ed9
- Loading branch information
Tres Seaver tseaver@palladion.com
authored and
Tres Seaver tseaver@palladion.com
committed
Mar 25, 2010
1 parent
91d286b
commit 24db52d
Showing
16 changed files
with
557 additions
and
97 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,62 +1,12 @@ | ||
compoze README | ||
============== | ||
|
||
Overview | ||
This package provides a script for creating ``setuptools``-compatible | ||
package indexes using packages downloaded from other indexes. | ||
|
||
This package provides a script for creating setuptools-compatible | ||
package indexes using packages downloaded from other indexes. | ||
Please see ``docs/index.rst`` for the documentation, which can also be | ||
read online at: | ||
|
||
Installation | ||
|
||
Installing 'compoze' via 'easy_install' (it doesn't | ||
depend on any other 'repoze' packages), creates a script, | ||
'compoze', in the scripts directory of your Python:: | ||
|
||
$ bin/easy_install -i http://dist.repoze.org/simple compoze | ||
|
||
Fetching Distributions | ||
|
||
The 'compoze fetch' command is useful for retrieving distutils | ||
distributions matching a set requirment specifications, e.g:: | ||
|
||
$ bin/compoze fetch --path=/tmp/index \ | ||
--index-url=http://dist.repoze.org/simple \ | ||
repoze.grok "repoze.project>=2.1" | ||
|
||
If you do not supply an index URL, 'compoze' uses the Python | ||
Package Index (the "cheeseshop") by default:: | ||
|
||
$ bin/compoze fetch --path=/tmp/index someproject | ||
|
||
You can supply more than one "source" index:: | ||
|
||
$ bin/compoze fetch --path=/tmp/index \ | ||
--index-url=http://example.com/index \ | ||
--index-url=http://another.example.com/index \ | ||
someproject another_project | ||
|
||
If you do not supply a path, 'compoze fetch' uses the current | ||
directory. | ||
|
||
Example: Recreating the Package Set Already Installed | ||
|
||
You can also ask to have 'compoze' fetch distributions for the eggs | ||
already installed in site-packges:: | ||
|
||
$ bin/compoze fetch --path=/tmp/plone --fetch-site-packages | ||
|
||
Building a Package Index | ||
|
||
'compoze index' will make a PyPI-like package index in the | ||
target directory:: | ||
|
||
$ bin/compoze index --path=/tmp/downloads | ||
|
||
Example: Creating a Package Index for the Versions Already Installed | ||
|
||
One common use case is to capture the "known good set" represented | ||
by a given Python environment. In this case, you want both to download | ||
the distributions corresponding to the projects installed in site-packages, | ||
and also make a package index from them:: | ||
|
||
$ bin/compoze fetch --fetch-site-packages --path kgs \ | ||
index --path kgs | ||
http://docs.repoze.org/compoze | ||
|
||
http://packages.python.org/compoze |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.