diff options
| -rw-r--r-- | INSTALL | 57 |
1 files changed, 30 insertions, 27 deletions
@@ -1,34 +1,33 @@ -facilityMailman - The GNU Mailing List Management System -Copyright (C) 1998 Free Software Foundation, Inc. +Mailman - The GNU Mailing List Management System +Copyright (C) 1998,1999,2000 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA -This file contains installation instructions. Mailman is configured -using the standard GNU autoconf software. You should first set up -your system as outlined in the sections below, and then configure and -install the Mailman software. +This file contains installation instructions for Mailman, which is +configured using the standard GNU autoconf software. You should first +set up your system as outlined in the sections below, and then +configure and install the Mailman software. UPGRADING: -Generally one can follow the below directions, giving the location of -the old install as the target directory, and the upgrade will happen -transparently. However, please read the notes in the file UPGRADING -if you want to keep your existing installation intact. +Upgrading is usually as easy as just installing the new version over +the existing installation. However, you should read the notes in the +file UPGRADING for important information before you upgrade. 0. Installation requirements You must have the Python interpreter installed somewhere on your - system. Currently Python 1.5 or later is required, but 1.5.1 is - recommended. For information about obtaining Python source code, - or pre-compiled binaries please see the Python Web site at + system. Currently Python 1.5.2 or later is required. For + information about obtaining Python source code, or pre-compiled + binaries please see the Python Web site at - <http://www.python.org/> + http://www.python.org - You must also have a C compiler in order to build the wrapper - programs which are used for improved security. The GNU C compiler - gcc 2.8.1 is known to work well. For more information about - obtaining gcc, see + 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 is known to work well. For more information + about obtaining gcc, see - <http://www.gnu.org/> + http://www.gnu.org 1. System setup @@ -42,8 +41,8 @@ if you want to keep your existing installation intact. - Add a new group called `mailman'. Typically this is added to your /etc/group file. The Mailman files will be installed under - the `mailman' group, with the set-group-id bit. This is so both - the Web based and mail based programs will have the proper write + the `mailman' group, with the set-group-id bit. This is so both + the Web based and mail based programs will have the proper write permissions. - Create an installation directory (called $prefix in the @@ -196,15 +195,19 @@ if you want to keep your existing installation intact. scripts run is *not* in the `mailman' group you created above, otherwise private archives will be accessible to anyone. - - Copy the Mailman logo file misc/mailman.jpg to a location - accessible to your Web server. E.g. with Apache, you might - create an images subdirectory inside htdocs, and then copy - misc/mailman.jpg to htdocs/images/mailman.jpg + - Copy the Mailman, Python, and GNU logos a location accessible to + your Web server. E.g. with Apache, you've usually got an + `icons' directory that you can drop the images into. You want + to copy misc/mailman.jpg, misc/PythonPowered.png, and + misc/gnu-head-tiny.jpg to this directory. You then want to add a line to your $prefix/Mailman/mm_cfg.py - file which sets the URL to the logo file. For example: + file which sets the base URL for the logos. For example: - DELIVERED_BY_URL = '/images/mailman.jpg' + IMAGE_LOGOS = '/images/' + + The default value for IMAGE_LOGOS is '/icons/'. Read the + comment in Defaults.py.in for details. - Configure your Web server to point to the Pipermail public mailing list archives: |