[Checkins] SVN: zc.sourcerelease/branches/dev/ ignore more
Jim Fulton
jim at zope.com
Wed Oct 24 18:30:29 EDT 2007
Log message for revision 81067:
ignore more
Changed:
_U zc.sourcerelease/branches/dev/
U zc.sourcerelease/branches/dev/setup.py
U zc.sourcerelease/branches/dev/src/zc/sourcerelease/README.txt
-=-
Property changes on: zc.sourcerelease/branches/dev
___________________________________________________________________
Name: svn:ignore
- develop-eggs
bin
parts
+ develop-eggs
bin
parts
doc.txt
doc.html
dist
Modified: zc.sourcerelease/branches/dev/setup.py
===================================================================
--- zc.sourcerelease/branches/dev/setup.py 2007-10-24 22:12:46 UTC (rev 81066)
+++ zc.sourcerelease/branches/dev/setup.py 2007-10-24 22:30:28 UTC (rev 81067)
@@ -1,10 +1,24 @@
+import os
from setuptools import setup, find_packages
+def read(*rnames):
+ return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
+
entry_points = """
[console_scripts]
buildout-source-release = zc.sourcerelease:source_release
"""
+long_description=(
+ read('src', 'zc', 'sourcerelease', 'README.txt')
+ + '\n' +
+ 'Download\n'
+ '**********************\n'
+ )
+
+open('doc.txt', 'w').write(long_description)
+
+
setup(
name = "zc.sourcerelease",
description = "Utility script to create source releases from buildouts",
@@ -12,6 +26,7 @@
license = "ZPL 1.0",
url='http://www.python.org/pypi/zc.sourcerelease',
author='Jim Fulton', author_email='jim at zope.com',
+ long_description=long_description,
entry_points = entry_points,
packages = find_packages('src'),
Modified: zc.sourcerelease/branches/dev/src/zc/sourcerelease/README.txt
===================================================================
--- zc.sourcerelease/branches/dev/src/zc/sourcerelease/README.txt 2007-10-24 22:12:46 UTC (rev 81066)
+++ zc.sourcerelease/branches/dev/src/zc/sourcerelease/README.txt 2007-10-24 22:30:28 UTC (rev 81067)
@@ -3,7 +3,7 @@
The zc.sourcerelease package provides a script,
buildout-source-release, that generates a source release from a
-buildout. The source release, in the form of a gzipped tar archive
+buildout. The source release, is in the form of a gzipped tar archive
[#zip_in_future]_. The generated source release can be used as the
basis for higher-level releases, such as RPMs or
configure-make-make-install releases.
@@ -17,12 +17,13 @@
installed.
The source release includes a Python install script. It is not
-executable and is run with the desired Python. The install script
-runs the buildout in place. This means that
-the source release will need to be extracted to and the buildout run
-in the final install location [#separate_install_step]_. While the
-install script can be used directly, it will more commonly be used by
-system-packaging (e.g. RPM) build scripts or make files.
+executable and must be run with the desired Python, which must be the
+same version of Python used when making the release. The install
+script runs the buildout in place. This means that the source release
+will need to be extracted to and the install script run in the final install
+location [#separate_install_step]_. While the install script can be
+used directly, it will more commonly be used by system-packaging
+(e.g. RPM) build scripts or make files.
To create a source release, simply run the buildout-source-release
script, passing a file URL or a subversion URL
@@ -106,7 +107,8 @@
d zc.buildout-99.99-py2.4.egg
Note that version 99.99 of zc.buildout was used because it was the
-most recent version on the link server. This happens to be different than the version of buildout used by the source-release script.
+most recent version on the link server. This happens to be different
+than the version of buildout used by the source-release script.
It has a release-distributions directory containing distributions
needed to install the buildout:
@@ -123,7 +125,7 @@
was downloaded from the link server. Anything that we downloaded is
included.)
-So, not that we've extracted the source release we built, we can try
+So, now that we've extracted the source release we built, we can try
to install it. To do this, we'll to run the installer.
>>> import sys
@@ -200,13 +202,15 @@
.. [#zip_in_future] It is possible that an option will be added in the
-future to generate zip files rather than tar archives.
+ future to generate zip files rather than tar archives.
.. [#separate_install_step] In the future, it is likely that we'll
-also support a model in which the install script can install to a
-separate location. Buildouts will have to take this into account,
-providing for copying necessary files, other than just scripts and
-eggs, into the destination directory.
+ also support a model in which the install script can install to a
+ separate location. Buildouts will have to take this into account,
+ providing for copying necessary files, other than just scripts and
+ eggs, into the destination directory.
.. [#other_source_code_control_systems] Other source
-code control systems may be supported in the future.
+ code control systems may be supported in the future. In the mean
+ time, you can check a project out to a directory and then use a file
+ URL to get the buildout-source-release script to use it.
More information about the Checkins
mailing list