TMDA Installation

>>> TMDA |  |
Home | Help | TMDA-CGI | SourceForge
[ AU | DE | IT | PL | US mirror ] | FAQ | Wiki | Store
1. > | ### TMDA Installation Installation from gzipped tarball Choose an installation location which can either be an individual area (such as within your home directory), or a shared area (such as /usr/local) for system-wide use, and change to that directory. Unpack the TMDA distribution.
   >     # gunzip -c tmda-0.01.tgz | tar xvf -
2. > If this is a system-wide install, run the compileall script to byte-compile all the .py files. Byte-compilation is optional, but will speed TMDA's start-up time. This will be done automatically by Python if you have write permissions in the installation directory, which is why it's not necessary for individual installs.
   >     # cd tmda-0.01
   >     # ./compileall
> TMDA is designed to run directly from its source directory. For example, if installed in /usr/local/tmda-0.01/, you'd run tmda-keygen by invoking `/usr/local/tmda-0.01/bin/tmda-keygen`. Do not move the bin/* programs outside the source tree, although making symlinks from other areas of the filesystem (such as /usr/local/bin) into the source tree will work fine. Installation from Linux RPMs If you are running Linux, you may wish to install TMDA via RPM instead. A binary RPM can be built and installed directly from the source tarball:
>     # rpmbuild -tb tmda-0.01.tgz
>     # rpm -Uvh /usr/src/redhat/RPMS/noarch/tmda-0.01-1.noarch.rpm
> If your system lacks a /usr/bin/python2, you may get a dependency warning from RPM. If you're sure your Python meets the requirements, then you can override this dependency check using the --nodeps option to RPM:
>     # rpmbuild -tb --nodeps tmda-0.01.tgz
>     # rpm -Uvh --nodeps /usr/src/redhat/RPMS/noarch/tmda-0.01-1.noarch.rpm
> Post-Installation Report your installation (used only to satisfy my curiosity about what platforms are using TMDA):
>     # tmda-keygen -V | mail jason-tmdausage@mastaler.com
Then proceed to the Configuration section.