Changes between Version 1 and Version 2 of Packaging

Timestamp:

2007-07-16T17:46:22Z (17 years ago)

Author:

zooko

Comment:

add notes about setuptools

Packaging

@@ -14 +14 @@
 
  * Make it convenient for someone to use other versions of the packages that we use e.g. system-wide packages or newer or alternate versions, etc..
+
+== setuptools ==
+
+One option is to use a Python packaging tool named [http://cheeseshop.python.org/pypi/setuptools setuptools].
+
+Advantages (note that each of these are options provided by setuptools, not requirements imposed by the use of setuptools):
+
+ * management of dependencies (even on platforms that don't have a native package manager);  This is the important feature.
+
+ * integration with http://cheeseshop.python.org/ -- with setuptools we can update the [http://cheeseshop.python.org/pypi/allmydata-tahoe allmydata-tahoe metadata at the cheeseshop] automatically, and also upload packages to be distributed from cheeseshop
+
+ * for hackers who want to use Tahoe, and who like setuptools, this makes using Tahoe convenient and pleasant for them
+
+ * replace "build/configure/package/distribute/test/develop" code written in the Make language with code written in Python;  One specific instance of this is {{{./setup.py test}}} which runs the unit tests
+
+Disadvantages:
+
+ * We haven't figured out exactly how to take advantage of setuptools's dependency management while also integrating smoothly with platform-specific package managers such as Debian apt.  I (Zooko) think that this is possible, but it isn't yet standard practice among setuptools users.  One important detail is the special option to setuptools called {{{--single-version-externally-managed}}}.