CVS: tmda/htdocs download.ht, 1.31, 1.32 download.html, 1.72, 1.73 install.ht, 1.15, 1.16 install.html, 1.57, 1.58
"Jason R. Mastaler" <[email protected]> Tue, 10 Feb 2004 14:06:18 -0800
| Newsgroups | gmane.mail.spam.tmda.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/tmda/tmda/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6518/htdocs Modified Files: download.ht download.html install.ht install.html Log Message: tmda.spec now depends on /usr/bin/python2.3 instead of /usr/bin/python2 since very few if any distros currently have Python 2.3 as their /usr/bin/python2. If they do, they will have a /usr/bin/python2.3 anyway. If they don't, the user can install an RPM from www.python.org which does not conflict with the currently installed Python RPM on the system. Index: download.ht =================================================================== RCS file: /cvsroot/tmda/tmda/htdocs/download.ht,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- download.ht 10 Feb 2004 00:13:24 -0000 1.31 +++ download.ht 10 Feb 2004 22:05:43 -0000 1.32 @@ -24,7 +24,7 @@ <ul> -<li><a href="install.html">Red Hat Linux RPM</a><br> +<li><a href="install.html#RPM">Red Hat Linux RPM</a><br> <li><a href="http://packages.debian.org/tmda" TARGET="Resource Window">Debian GNU/Linux</a><br> Index: download.html =================================================================== RCS file: /cvsroot/tmda/tmda/htdocs/download.html,v retrieving revision 1.72 retrieving revision 1.73 diff -u -r1.72 -r1.73 --- download.html 10 Feb 2004 00:13:24 -0000 1.72 +++ download.html 10 Feb 2004 22:05:43 -0000 1.73 @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Mon Feb 9 17:14:14 2004 --> +<!-- Tue Feb 10 12:06:12 2004 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -232,7 +232,7 @@ <ul> -<li><a href="install.html">Red Hat Linux RPM</a><br> +<li><a href="install.html#RPM">Red Hat Linux RPM</a><br> <li><a href="http://packages.debian.org/tmda" TARGET="Resource Window">Debian GNU/Linux</a><br> Index: install.ht =================================================================== RCS file: /cvsroot/tmda/tmda/htdocs/install.ht,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- install.ht 12 Mar 2003 21:12:12 -0000 1.15 +++ install.ht 10 Feb 2004 22:05:44 -0000 1.16 @@ -2,16 +2,14 @@ <h3>TMDA Installation</h3> -<u>Installation from gzipped tarball</u><br><br> +<u>Installation from gzipped source tarball</u><br><br> 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.<br><br> +for system-wide use, and change to that directory.<br> <ol> <li>Unpack the TMDA distribution.<br> <blockquote><pre> - -# gunzip -c tmda-0.01.tgz | tar xvf - - +# gunzip -c tmda-1.1.0.tgz | tar xvf - </pre></blockquote> <li>If this is a system-wide install, run the <strong>compileall</strong> @@ -21,45 +19,36 @@ installation directory, which is why it's not necessary for individual installs. <blockquote><pre> - -# cd tmda-0.01 +# cd tmda-1.1.0 # ./compileall - </pre></blockquote> <li>TMDA is designed to run directly from its source directory. For -example, if installed in /usr/local/tmda-0.01/, you'd run <b>tmda-keygen</b> -by invoking <code>/usr/local/tmda-0.01/bin/tmda-keygen</code>. Do not +example, if installed in /usr/local/tmda-1.1.0/, you'd run <b>tmda-keygen</b> +by invoking <code>/usr/local/tmda-1.1.0/bin/tmda-keygen</code>. 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. </ol> -<u>Installation from Linux RPMs</u><br><br> +<u><a name="RPM">Installation from Linux RPM</a></u><br><br> -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: +If you are running an RPM-compatible distro of Linux, you may wish to +install TMDA via RPM instead. A binary RPM can be built and installed +directly from the source tarball: <blockquote><pre> - -# rpmbuild -tb tmda-0.01.tgz -# rpm -Uvh /usr/src/redhat/RPMS/noarch/tmda-0.01-1.noarch.rpm - +# rpmbuild -tb tmda-1.1.0.tgz +# rpm -Uvh /usr/src/redhat/RPMS/noarch/tmda-1.1.0-1.noarch.rpm </pre></blockquote> -If your system lacks a <b>/usr/bin/python2</b>, you may get a -dependency warning from RPM. If you're sure your Python meets the -<a href="requirements.html">requirements</a>, then you can override this -dependency check using the <em>--nodeps</em> option to RPM: - -<blockquote><pre> - -# rpmbuild -tb --nodeps tmda-0.01.tgz -# rpm -Uvh --nodeps /usr/src/redhat/RPMS/noarch/tmda-0.01-1.noarch.rpm - -</pre></blockquote> +If your system lacks a <b>/usr/bin/python2.3</b> binary, you will get +a dependency error from rpmbuild. The solution is to install a +<a href="http://www.python.org/2.3.3/rpms.html" TARGET="Resource Window"> +Python 2.3.x RRM from python.org</a>. As explained on their page, this will +not conflict with or overwrite your system's existing Python in any way. +<br><br> <u>Post-Installation</u><br><br> Index: install.html =================================================================== RCS file: /cvsroot/tmda/tmda/htdocs/install.html,v retrieving revision 1.57 retrieving revision 1.58 diff -u -r1.57 -r1.58 --- install.html 6 Feb 2004 17:57:05 -0000 1.57 +++ install.html 10 Feb 2004 22:05:44 -0000 1.58 @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Fri Feb 6 10:40:30 2004 --> +<!-- Tue Feb 10 12:08:05 2004 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -210,16 +210,14 @@ <td valign="top" width="90%" class="body"><br> <h3>TMDA Installation</h3> -<u>Installation from gzipped tarball</u><br><br> +<u>Installation from gzipped source tarball</u><br><br> 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.<br><br> +for system-wide use, and change to that directory.<br> <ol> <li>Unpack the TMDA distribution.<br> <blockquote><pre> - -# gunzip -c tmda-0.01.tgz | tar xvf - - +# gunzip -c tmda-1.1.0.tgz | tar xvf - </pre></blockquote> <li>If this is a system-wide install, run the <strong>compileall</strong> @@ -229,45 +227,36 @@ installation directory, which is why it's not necessary for individual installs. <blockquote><pre> - -# cd tmda-0.01 +# cd tmda-1.1.0 # ./compileall - </pre></blockquote> <li>TMDA is designed to run directly from its source directory. For -example, if installed in /usr/local/tmda-0.01/, you'd run <b>tmda-keygen</b> -by invoking <code>/usr/local/tmda-0.01/bin/tmda-keygen</code>. Do not +example, if installed in /usr/local/tmda-1.1.0/, you'd run <b>tmda-keygen</b> +by invoking <code>/usr/local/tmda-1.1.0/bin/tmda-keygen</code>. 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. </ol> -<u>Installation from Linux RPMs</u><br><br> +<u><a name="RPM">Installation from Linux RPM</a></u><br><br> -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: +If you are running an RPM-compatible distro of Linux, you may wish to +install TMDA via RPM instead. A binary RPM can be built and installed +directly from the source tarball: <blockquote><pre> - -# rpmbuild -tb tmda-0.01.tgz -# rpm -Uvh /usr/src/redhat/RPMS/noarch/tmda-0.01-1.noarch.rpm - +# rpmbuild -tb tmda-1.1.0.tgz +# rpm -Uvh /usr/src/redhat/RPMS/noarch/tmda-1.1.0-1.noarch.rpm </pre></blockquote> -If your system lacks a <b>/usr/bin/python2</b>, you may get a -dependency warning from RPM. If you're sure your Python meets the -<a href="requirements.html">requirements</a>, then you can override this -dependency check using the <em>--nodeps</em> option to RPM: - -<blockquote><pre> - -# rpmbuild -tb --nodeps tmda-0.01.tgz -# rpm -Uvh --nodeps /usr/src/redhat/RPMS/noarch/tmda-0.01-1.noarch.rpm - -</pre></blockquote> +If your system lacks a <b>/usr/bin/python2.3</b> binary, you will get +a dependency error from rpmbuild. The solution is to install a +<a href="http://www.python.org/2.3.3/rpms.html" TARGET="Resource Window"> +Python 2.3.x RRM from python.org</a>. As explained on their page, this will +not conflict with or overwrite your system's existing Python in any way. +<br><br> <u>Post-Installation</u><br><br>