From 611b080c676e51772c2162298558f1cddc9d9630 Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Tue, 17 May 2011 21:02:28 +0000
Subject: [PATCH] move a packaging tip and trick to here from TipsTricks

[Imported from Trac: page Packaging, version 25]
---
 Packaging.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Packaging.md b/Packaging.md
index 8ea9931..b5e01ee 100644
--- a/Packaging.md
+++ b/Packaging.md
@@ -15,6 +15,12 @@ The goal is to start with a bare OS and a network connection (no Python, no comp
 
 For quickstart.html to work on your platform there *must* exist a binary .egg for your platform of every dependency which has a native-code extension module. Currently those are: pycryptopp, zfec, pywin32, and PyCrypto. If there is not a binary .egg available of one of those packages for a given platform then this is a bug which prevents quickstart.html 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 not a 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.html cannot instruct the user to do that (see the section about quickstart.html above), then the absence of a binary .egg of a dependency for a platform is a bug preventing quickstart.html from working on that platform.)
 
+#### Creating binary egg for pycrypto
+
+Juste add this line to setup.py: `from setuptools import setup, Extension`
+
+and run: `python setup.py bdist_egg`
+
 ## [AdvancedInstall](AdvancedInstall)
 
 An alternative method to quickstart.html, is [AdvancedInstall](AdvancedInstall). This method would be appropriate for people who prefer for the setup to be done differently than the way quickstart.html works. It is also the fallback for people who have tried quickstart.html and it didn't work (although the fact that quickstart.html didn't work should also be treated as a build process bug even if falling back to [AdvancedInstall](AdvancedInstall) allows the user to proceed).