Changes between Version 42 and Version 43 of Packaging

Timestamp:

2013-05-30T21:40:14Z (11 years ago)

Author:

daira

Comment:

fix command to build a pycrypto egg; add info about building other eggs

Packaging

@@ -37 +37 @@
 === binary .egg's of dependency native-code packages ===
 
-For quickstart.rst to work on your platform there ''must'' exist a binary .egg for your platform of every dependency that has a native-code extension module, which are listed in the columns of [http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html this table]. If there is no binary .egg available of one of those packages for a given platform then this is a bug which prevents quickstart.rst from working on that platform. (Note: if you already had that Python package installed on your system then you would be able to setup Tahoe-LAFS even if there is no binary egg of that Python package available, e.g. if you manually installed the package already or if you installed the package already using an operating system packaging tool like apt-get. Nonetheless, since we can't rely on the user having done that and since quickstart.rst cannot instruct the user to do that -- see the section about quickstart.rst above -- then the absence of a binary .egg of a dependency for a platform is a bug preventing quickstart.rst from working on that platform.)
+For quickstart.rst to work on your platform there ''must'' exist a binary .egg for your platform of each dependency that has a native-code extension module, which are listed in the columns of [http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html this table]. If there is no binary .egg available of one of those packages for a given platform then this is a bug which prevents quickstart.rst from working on that platform. (Note: if you already had that Python package installed on your system then you would be able to setup Tahoe-LAFS even if there is no binary egg of that Python package available, e.g. if you manually installed the package already or if you installed the package already using an operating system packaging tool like apt-get. Nonetheless, since we can't rely on the user having done that and since quickstart.rst cannot instruct the user to do that -- see the section about quickstart.rst above -- then the absence of a binary .egg of a dependency for a platform is a bug preventing quickstart.rst from working on that platform.)
+
+The eggs are built from the corresponding source packages:
+
+ * [http://twistedmatrix.com/trac/wiki/Downloads Twisted] (use the source tarball)
+ * [https://pypi.python.org/pypi/pyOpenSSL pyOpenSSL]
+ * [https://pypi.python.org/pypi/pycrypto pycrypto]
+ * [https://pypi.python.org/pypi/pycryptopp pycryptopp]
+ * [https://pypi.python.org/pypi/zfec zfec]
+ * [https://pypi.python.org/pypi/zope.interface zope.interface]
+
+Except for !PyCrypto (see below), each egg is built by running {{{python setup.py bdist_egg}}} in the root of its source distribution.
 
 ==== Creating a binary egg for !PyCrypto ====
@@ -43 +54 @@
 !PyCrypto's {{{setup.py}}} does not support setuptools, so the {{{bdist_egg}}} target is not available out of the box. To build an egg, use the following command:
 
-{{{$ python -c "import setuptools; execfile('setup.py')" bdist_egg}}}
+{{{$ python -c "import setuptools; __file__ = 'setup.py'; execfile('setup.py')" bdist_egg}}}
 
 Detailed instructions for building a !PyCrypto egg on Windows: HowtoBuildPyCryptoOnWindows.