mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-04-14 06:06:40 +00:00
further update the notes about the dependencies
This commit is contained in:
parent
594a37da18
commit
0544e0f39b
72
README
72
README
@ -13,19 +13,25 @@ API is different than the normal Crypto package). It also includes Zooko's
|
||||
PyFEC library, a fast python wrapper around the Rizzo 'fec' C library,
|
||||
installed to the 'zfec' package and located in src/zfec/ .
|
||||
|
||||
|
||||
DEPENDENCIES:
|
||||
|
||||
Note: Except for Foolscap, all of the following dependencies can probably be
|
||||
installed through your standard package management tool if you are running on
|
||||
a modern Unix operating system. If you are running any modern Linux or *BSD
|
||||
distribution then you can almost certainly get them through your standard
|
||||
package manager. If you are running Mac OS X then the "fink" package
|
||||
management tool does not have most of these packages, but the "darwinports"
|
||||
package management tool appears to have them. If you are running on Windows
|
||||
then I'm afraid you'll have to install them by hand (although the "cygwin"
|
||||
package management tool does have some of them). If you are running on
|
||||
Solaris, I would like to hear from you -- I have no idea how it is done on
|
||||
Solaris nowadays.
|
||||
Note: Except for Foolscap, all of the following dependencies can
|
||||
probably be installed through your standard package management tool
|
||||
if you are running on a modern Unix operating system. If you are
|
||||
running any modern Linux or *BSD distribution then you can almost
|
||||
certainly get them through your standard package manager. If you are
|
||||
running Mac OS X then the "fink" package management tool does not
|
||||
have most of these packages, but the "darwinports" package management
|
||||
tool appears to have them. If you are running on Windows then I'm
|
||||
afraid you'll have to install them by hand (although the "cygwin"
|
||||
package management tool does have some of them). If you are running
|
||||
on Solaris, I would like to hear from you -- I have no idea how it is
|
||||
done on Solaris nowadays.
|
||||
|
||||
* a C compiler (language)
|
||||
|
||||
* GNU make (build tool)
|
||||
|
||||
* Python 2.4 or newer (tested against 2.4, 2.5, and 2.5.1), but v2.5 or
|
||||
higher is required on Windows-native) (language)
|
||||
@ -35,8 +41,8 @@ Solaris nowadays.
|
||||
integration library)
|
||||
http://twistedmatrix.com/
|
||||
|
||||
You need the following subpackages (which are are included in the default
|
||||
Twisted distribution):
|
||||
You need the following subpackages (which are included in the
|
||||
default Twisted distribution):
|
||||
|
||||
* core (the standard Twisted package)
|
||||
* web, trial, conch
|
||||
@ -44,6 +50,27 @@ Solaris nowadays.
|
||||
Twisted requires zope.interface, a copy of which is included in the Twisted
|
||||
distribution.
|
||||
|
||||
* Nevow (probably 0.9.0 or later) (web presentation language)
|
||||
http://divmod.org/trac/wiki/DivmodNevow
|
||||
|
||||
* setuptools (build and distribution tool)
|
||||
http://peak.telecommunity.com/DevCenter/EasyInstall#installation-instructions
|
||||
|
||||
* PyOpenSSL (0.6 or later) (secure transport layer)
|
||||
http://pyopenssl.sourceforge.net
|
||||
|
||||
For Windows-native, download this:
|
||||
http://allmydata.org/source/pyOpenSSL-0.6.win32-py2.5.exe
|
||||
|
||||
* to build the debian packages you will need all the usual debian-packaging
|
||||
tools, which means the 'build-essential' metapackage and all of the
|
||||
packages listed as "Build-Depends" in DIST/debian/control for your
|
||||
distribution. You will also want the 'fakeroot' package to allow the
|
||||
top-level 'make deb-DIST' targets work.
|
||||
|
||||
* on Windows, the pywin32 package
|
||||
http://sourceforge.net/projects/pywin32/
|
||||
|
||||
* Foolscap (0.1.2 or newer) (remote object library)
|
||||
http://twistedmatrix.com/trac/wiki/FoolsCap
|
||||
|
||||
@ -51,24 +78,6 @@ Solaris nowadays.
|
||||
release to the next, make sure all of your nodes are using the same version
|
||||
of Foolscap
|
||||
|
||||
* Nevow (probably 0.9.0 or later) (web presentation language)
|
||||
http://divmod.org/trac/wiki/DivmodNevow
|
||||
|
||||
* PyOpenSSL (0.6 or later) (secure transport layer)
|
||||
http://pyopenssl.sourceforge.net
|
||||
|
||||
* setuptools (build and distribution tool)
|
||||
http://peak.telecommunity.com/DevCenter/EasyInstall#installation-instructions
|
||||
|
||||
* a C compiler (language)
|
||||
|
||||
* GNU make (build tool)
|
||||
|
||||
* to build the debian packages you will need all the usual debian-packaging
|
||||
tools, which means the 'build-essential' metapackage and all of the
|
||||
packages listed as "Build-Depends" in DIST/debian/control for your
|
||||
distribution. You will also want the 'fakeroot' package to allow the
|
||||
top-level 'make deb-DIST' targets work.
|
||||
|
||||
BUILDING:
|
||||
|
||||
@ -82,6 +91,7 @@ BUILDING:
|
||||
|
||||
'make test' runs the unit test suite.
|
||||
|
||||
|
||||
INSTALLING:
|
||||
|
||||
If you're running on a debian system, use 'make deb-dapper' or 'make
|
||||
|
Loading…
x
Reference in New Issue
Block a user