From 0b5de876d3d1f915e6485a249f3e65749b437709 Mon Sep 17 00:00:00 2001 From: markus schnalke Date: Mon, 2 Jan 2012 10:20:49 +0100 Subject: [PATCH] Updated INSTALL and changed `nmh' strings to `mmh' --- INSTALL | 74 ++++++++++++++++++++++++----------------------------- config/version.sh | 6 ++--- configure.ac | 12 ++++----- 3 files changed, 43 insertions(+), 49 deletions(-) diff --git a/INSTALL b/INSTALL index 179d11d..7d86fe3 100644 --- a/INSTALL +++ b/INSTALL @@ -3,16 +3,16 @@ # -------------- -Installing nmh +Installing mmh -------------- Please read all of the following instructions before you begin -building nmh. +building mmh. You should check the MACHINES file to see if there are any specific -build instructions for your operating system. To build nmh, you will +build instructions for your operating system. To build mmh, you will need an ANSI C compiler such as gcc. -0) If you have obtained nmh by checking it out of CVS, you will +0) If you have obtained mmh by checking it out of git, you will need to run the GNU autotools to regenerate some files. (If your directory already contains a file 'config.h.in' then this has already been done and you do not need to do it.) @@ -20,7 +20,7 @@ need an ANSI C compiler such as gcc. ./autogen.sh - (Note that if you're doing nmh development, you should look at + (Note that if you're doing mmh development, you should look at docs/README.developers, since there is other developer-friendly advice there as well.) @@ -47,14 +47,13 @@ need an ANSI C compiler such as gcc. Note that if you have [n]mh files in your install directories with the same names as the files being installed, the old ones will get - overwritten without any warning. The only directory that isn't - true for is the `etc' directory -- in that directory, the previous - copy of each will be backed up as .prev if it differs - from the newly-installed copy. Watch for any diff output while - make is processing that directory to see if you need to merge - changes from *.prev files into the new versions. - -5) Edit the file `mts.conf' (installed in the nmh `etc' directory) + overwritten without any warning. The only directory this isn't + true for, is the `etc' directory -- in that directory, the distributed + files are installed with a `.dist' suffix if they differ from the + existing file. Watch for information messages while make is processing + that directory to see if you need to merge changes. + +5) Edit the file `mts.conf' (installed in the mmh `etc' directory) and make any necessary changes for the mail transport interface you are using. @@ -63,11 +62,11 @@ need an ANSI C compiler such as gcc. injecting the message to a mail transfer agent (such as sendmail) on the local machine. - Check the `mh-tailor' man page for a list of all the available options - for this file ("masquerade" may be of particular interest). + Check the `mts.conf(5)' man page for a list of all the available + options for this file ("masquerade" may be of particular interest). -6) Edit the file `mhn.defaults' (installed in the nmh `etc' directory). - This file contains the default profile entries for the nmh commands +6) Edit the file `mhn.defaults' (installed in the mmh `etc' directory). + This file contains the default profile entries for the mmh commands mhlist/mhstore/mhshow and is created by the script `mhn.defaults.sh'. This script will search a generic path (essentially your $PATH) for programs to handle various content types (for example, xv to display @@ -78,7 +77,7 @@ need an ANSI C compiler such as gcc. % cd support/general % ./mhn.defaults.sh /usr/local/bin:/usr/X11/bin:/usr/ucb > mhn.defaults - and then move `mhn.defaults' into the nmh `etc' directory. + and then move `mhn.defaults' into the mmh `etc' directory. The `mhn.defaults.sh' script only searches for a simple set of programs. If you have specialized programs to handle various types, you will need @@ -87,11 +86,6 @@ need an ANSI C compiler such as gcc. Programmers", 3rd edition, by Jerry Peek, on the Internet at . -7) Add an optional global mh.profile, if desired. This profile should be - placed in the nmh `etc' directory with the name `mh.profile'. This - file will be used to construct the initial .mh_profile of a new nmh - user, but will not be consulted after that. - ----------------------------------------------- Compiler options, or using a different compiler ----------------------------------------------- @@ -109,18 +103,18 @@ Or on systems that have the "env" program, you can do it like this: env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure ---------------------------------------- -Building nmh on additional architectures +Building mmh on additional architectures ---------------------------------------- -To build nmh on additional architectures, you can do a "make distclean". -This should restore the nmh source distribution back to its original -state. You can then configure nmh as above on other architectures in -which you wish to build nmh. Or alternatively, you can use a different +To build mmh on additional architectures, you can do a "make distclean". +This should restore the mmh source distribution back to its original +state. You can then configure mmh as above on other architectures in +which you wish to build mmh. Or alternatively, you can use a different build directory for each architecture. --------------------------------- Using a different build directory --------------------------------- -You can compile the nmh in a different directory from the one containing +You can compile the mmh in a different directory from the one containing the source code. Doing so allows you to compile it on more than one architecture at the same time. To do this, you must use a version of "make" that supports the "VPATH" variable, such as GNU "make". "cd" to @@ -128,29 +122,29 @@ the directory where you want the object files and executables to go and run the "configure" script. "configure" automatically checks for the source code in the directory that "configure" is in. For example, - cd /usr/local/solaris/nmh - /usr/local/src/nmh-1.0/configure + cd /usr/local/solaris/mmh + /usr/local/src/mmh-1.0/configure make --------------------- Options for configure --------------------- ---prefix=DIR (DEFAULT is /usr/local/nmh) +--prefix=DIR (DEFAULT is /usr/local/mmh) This will change the base prefix for the installation location - for the various parts of nmh. Unless overridden, nmh is installed + for the various parts of mmh. Unless overridden, mmh is installed in ${prefix}/bin, ${prefix}/etc, ${prefix}/lib, ${prefix}/man. --bindir=DIR (DEFAULT is ${prefix}/bin) - nmh's binaries (show, inc, comp, ...) are installed here. + mmh's binaries (show, inc, comp, ...) are installed here. --libdir=DIR (DEFAULT is ${prefix}/lib) - nmh's support binaries (spost, slocal, mhl, ...) are installed here. + mmh's support binaries (spost, slocal, mhl, ...) are installed here. --sysconfdir=DIR (DEFAULT is ${prefix}/etc) - nmh's config files (mts.conf, mhn.defaults, ...) are installed here. + mmh's config files (mts.conf, mhn.defaults, ...) are installed here. --mandir=DIR (DEFAULT is ${prefix}/man) - nmh's man pages are installed here. + mmh's man pages are installed here. --enable-debug Enable debugging support. @@ -159,7 +153,7 @@ Options for configure If this option is disabled, the mts.conf file will contain the line "masquerade: " (with no value), which may be manually edited later. You may find it convenient to specify a value at - configure-time, however, so that each time nmh is reinstalled, + configure-time, however, so that each time mmh is reinstalled, the right value will be there. By default, it is enabled. The above usage shows the default, with all three masquerade @@ -198,5 +192,5 @@ Options for configure specified. -- -The nmh team -nmh-workers@nongnu.org +markus schnalke +and the nmh team diff --git a/config/version.sh b/config/version.sh index 61d9637..5a9628c 100755 --- a/config/version.sh +++ b/config/version.sh @@ -1,6 +1,6 @@ #!/bin/sh # -# version.sh -- script to create version string(s) for nmh. +# version.sh -- script to create version string(s) for mmh. # # You need to pass the script the version number to use. # @@ -40,5 +40,5 @@ done IFS=" " -echo "char *version_str = \"nmh-$VERSION [compiled on $HOSTNAME at `date`]\";" -echo "char *version_num = \"nmh-$VERSION\";" +echo "char *version_str = \"mmh-$VERSION [compiled on $HOSTNAME at `date`]\";" +echo "char *version_num = \"mmh-$VERSION\";" diff --git a/configure.ac b/configure.ac index 35d1b2d..b3fa70a 100644 --- a/configure.ac +++ b/configure.ac @@ -1,5 +1,5 @@ dnl -dnl configure.ac -- autoconf template for nmh +dnl configure.ac -- autoconf template for mmh dnl dnl Move this up a bit @@ -28,16 +28,16 @@ fi echo "configuring for AC_PACKAGE_NAME-AC_PACKAGE_VERSION" AC_SUBST(VERSION,AC_PACKAGE_VERSION)dnl -dnl What date of nmh are we building? +dnl What date of mmh are we building? DATE=`cat ${srcdir}/DATE` -echo "configuring for nmh dated $DATE" +echo "configuring for mmh dated $DATE" AC_SUBST(DATE)dnl dnl -------------------------- dnl CHECK COMMAND LINE OPTIONS dnl -------------------------- -dnl Do you want to debug nmh? +dnl Do you want to debug mmh? AC_ARG_ENABLE(debug, AS_HELP_STRING([--enable-debug],[enable nmh code debugging])) dnl The old redundant --enable-nmh-debug is deprecated and undocumented. @@ -825,9 +825,9 @@ eval "nmhlib=${libdir}"; eval "nmhlib=${nmhlib}" eval "nmhman=${mandir}"; eval "nmhman=${nmhman}" echo " -nmh configuration +mmh configuration ----------------- -nmh version : AC_PACKAGE_VERSION +mmh version : AC_PACKAGE_VERSION target os : ${target} compiler : ${CC} compiler flags : ${CFLAGS} -- 1.7.10.4