Update of /cvsroot/mailman/mailman
In directory usw-pr-cvs1:/tmp/cvs-serv10517
Modified Files:
INSTALL
Log Message:
Updates
Index: INSTALL
===================================================================
RCS file: /cvsroot/mailman/mailman/INSTALL,v
retrieving revision 2.12
retrieving revision 2.13
diff -C2 -d -r2.12 -r2.13
*** INSTALL 23 Feb 2002 06:17:39 -0000 2.12
--- INSTALL 16 Mar 2002 05:25:26 -0000 2.13
***************
*** 16,22 ****
0. Installation requirements
You must have the Python interpreter installed somewhere on your
! system. Currently Python 2.0 or later is required, although
! Python 2.1.1 or Python 2.2 is recommended. For information about
obtaining Python source code, RPM packages, or pre-compiled
binaries please see:
--- 16,33 ----
0. Installation requirements
+ You must have a mail server (MTA) that you can send messages to,
+ and a web server that supports the CGI/1.1 API. Apache makes a
+ fine choice for web server, and MTAs such as Postfix, Exim, and
+ Sendmail should work just fine.
+
+ You will need an ANSI C compiler to build Mailman's security
+ wrappers. The GNU C compiler gcc 2.8.1 or later is known to work
+ well. For more information about obtaining gcc, see
+
+ http://www.gnu.org
+
You must have the Python interpreter installed somewhere on your
! system. Currently Python 2.1 or later is required; Python
! 2.1.2 or Python 2.2 is recommended. For information about
obtaining Python source code, RPM packages, or pre-compiled
binaries please see:
***************
*** 30,40 ****
stick to the basics that compile on most systems.
- You must also have an ANSI C compiler in order to build the
- wrapper programs which are used for improved security. The GNU C
- compiler gcc 2.8.1 or later is known to work well. For more
- information about obtaining gcc, see
-
- http://www.gnu.org
-
If there is a README.<yourMTA> file that describes your mail
server (MTA), read it now. Some MTAs are more compatible with
--- 41,44 ----
***************
*** 77,81 ****
If you're upgrading from a version previous to Mailman2.1alpha2,
you will need to use --prefix unless you move your mailing
! lists.
Watch out if your site does something like mount /usr/local with
--- 81,85 ----
If you're upgrading from a version previous to Mailman2.1alpha2,
you will need to use --prefix unless you move your mailing
! lists (this can be a wise upgrade strategy).
Watch out if your site does something like mount /usr/local with
***************
*** 342,345 ****
--- 346,355 ----
(Note that /etc/init.d may be /etc/rc.d/init.d on some systems.)
+ On Debian, you probably want to use
+
+ % update-rc.d mailman defaults
+
+ instead of chkconfig.
+
For Unixes that don't support chkconfig, simply copy
misc/mailman as above, then set up the following symbolic links,
***************
*** 372,375 ****
--- 382,388 ----
% bin/newlist mailman
+
+ Follow the prompts, and see the README file for more
+ information.
- You should then subscribe yourself to the mailman list.
_______________________________________________
Mailman-checkins mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-checkins
