DataMuseum.dk

top - metrics - download

    Length: 28714 (0x702a)
    Types: TextFile
    Names: »EDITME-dist«

└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit
    └─⟦2fafebccf⟧ »EurOpenD3/mail/smail3.1.19.tar.Z« 
        └─⟦bcd2bc73f⟧ 
            └─⟦this⟧ »conf/EDITME-dist« 

TextFile

# @(#)EDITME-dist	1.41 3/26/89 15:34:39
#
# EDITME - edit me to perform high level configuration of smail
#
# The EDITME file is used by makefiles to build individual defs.h,
# defs.sh and defs.sed files, which in turn control the build/install
# process of smail.
#
# The EDITME-dist file servers as a reference copy only.  Patches to
# smail will refer to EDITME-dist rather than EDITME.  Only the EDITME
# file is used in the build/install process.  Any editing should be done
# to the file EDITME, which should be located in the same directory as
# EDITME-dist.
#
# The EDITME is a /bin/sh shell script.  That is, comments begin with
# the first non-quoted/non-escaped '#' character.  Values are set
# using NAME=VALUE or NAME=, with no spaces around the equal sign.
# Values that have spaces or special shell characters should be
# qouted and/or escaped.  Consult the sh(1) man page for further details.
#
# Values that are indicated as optional may, in some cases, not be set.
# All other values MUST be set to some value.  The NAME= form is
# equivalent to not setting the value, with the exception of TEST_BASE.
#
# An alternate path to the EDITME file can be specified through setting
# the environment variable SMAIL_EDITME.  This can either be a full
# pathname or a relateive pathname, which will be referenced relative
# to the smail conf directory.  Care must be taken with dependencies in
# makefiles when the path to the EDITME file has changed.  If this is
# a permanent change, then type "make depend" at the top of the smail
# source tree.  Otherwise the conf/lib/mkdefs.sh shell script can be
# run in affected directories to create new defs files.


# CFLAGS - the base set of flags for the cc command
#
# optional
#
# When debugging smail, it is useful to set this to "-g".  Otherwise
# "-O" is normally used to optimize the code produced.

CFLAGS=-O					# common
#CFLAGS=-g					# debug
#CFLAGS="-O -C"					# UTS/580
#CFLAGS="-g -C"					# UTS/580 debug


# LDFLAGS - flags to pass to the loader, including special libraries
#
# optional
#
# These flags are passed to the cc command after any libraries or
# flags specified in the conf/os file entry.

#LDFLAGS="-lc_s"				# System V.3 shared libc
#if [ "$FROM_ROOT" = src ]; then		# The BIND resolver library
#	LDFLAGS="-lresolv"			#  only used in the src
#fi						#  directory


# STRIP - define this if you wish to strip binaries when installing
#
# optional
#
# The smail binaries will only be striped on installation if STRIP=yes.
# This may save some disk space at the expence of the ability to do
# symbolic debugging.

#STRIP=yes


# USE_SYMLINKS - define this if you wish to use symlinks when installing
#
# optional
#
# The smail binaries are normally installed using hardlinks between
# the various copies of the smail binary.  Where hardlinks cannot be
# made, real copies are made.  To use symbolic links instead of
# hard links and copies, set USE_SYMLINKS=yes.  This will cause only
# one copy of the smail binary to be installed.  Do not define this
# if your system does not have symbolic links.  Also, do not define
# this if your UUCP (for some reason) cannot handle /bin/rmail being
# a symbolic link.

#USE_SYMLINKS=yes


# OS_TYPE - define the operating system type for your machine
#
# Consult the conf/os directory for a complete list of recognized
# operating system types.  The names given below may not represent
# all of the operating systems for which an OS description file
# is available.

#OS_TYPE=bsd4.2				# 4.2 BSD systems
OS_TYPE=bsd4.3				# 4.3 BSD systems
#OS_TYPE=cpc3.0				# Counterpoint C-XIX Release 3.0
#OS_TYPE=forpro				# fortune FOR:Pro 2.1 to 3.1
#OS_TYPE=stride2.2			# UniStride release 2.2
#OS_TYPE=sun_os3			# Sun/OS version 3.x
#OS_TYPE=sun_os4			# Sun/OS version 4.x
#OS_TYPE=sys5.2				# System V release 2
#OS_TYPE=sys5.3				# System V release 3
#OS_TYPE=ultrix1.2			# DEC Ultrix release 1.2
#OS_TYPE=unixpc3.0			# AT&T Unix PC (3b1) release 3.0
#OS_TYPE=unixpc3.5			# AT&T Unix PC (3b1) release 3.5
#OS_TYPE=uts1.2				# UTS/580 release 1.2
#OS_TYPE=uts2.0				# UTS/580 release 2.0 load0
#OS_TYPE=xenix5				# SCO Xenix System V


# ARCH_TYPE - architecture type
#
# The ARCH_TYPE of 16bit refers to machines with 16 bit words.  This
# mode is untested.  It is assumed that 16bit machines have extended
# address spaces as smail is more than 64k bytes long.

ARCH_TYPE=32bit					# common
#ARCH_TYPE=small32bit				# 32 bit without reasonable VM
#ARCH_TYPE=16bit				# untested


# DRIVER_CONFIGURATION - configuration file describing smail drivers
#
# optional
#
# By default, the os configuration file (conf/os/OS_TYPE) refers to
# the file that describes the available director, router and transport
# drivers.

# For example on BSD based OS_TYPEs, the os configuration file refers to
# a driver configuration that uses BSD networking.  A BSD based system
# could not set DRIVER_CONFIGURATION and get the BSD netwokring based
# drivers; or a system could set DRIVER_CONFIGURATION=unix-generic and
# disable BSD networking drivers.
#
# Currently there are no conf/os files which specify the arpa-network
# driver configuration (which includes support for the BIND server).
# If you want to use this, you must set DRIVER_CONFIGURATION
# explicitly.

DRIVER_CONFIGURATION=				# common, implied by os/OS_TYPE
#DRIVER_CONFIGURATION=unix-generic		# no BSD networking
#DRIVER_CONFIGURATION=$ROOT/mydriver.cf		# customized configuration
#DRIVER_CONFIGURATION=arpa-network		# include bind router


# HOSTNAMES - names for the local host
#
# optional
#
# The HOSTNAMES value is a colon-separated list of names your system.
# This does not need to include the name given by UUCP_NAME.  If
# HOSTNAMES is set, then the first name in the list will be used as the
# canonical name of your system.  That is, the name by which your
# machine can be uniquely named across all networks.
#
# Normally HOSTNAMES is not set.  In this case the HOSTNAMES value will
# be computed at run-time from the DOMAINS value and the system-dependently
# computed name of your system.
#
# If you are registered in a domain, you might consider seting HOSTNAMES
# to a list such as:   sitename.subdom.dom:sitename.foo.bar:sitename.uucp

#HOSTNAMES=kgbvax.ussr.comm:kgbvax.uucp		# example only


# DOMAINS - domains under which the local host resides
#
# optional   (except when HOSTNAMES is not set)
#
# If HOSTNAMES is not defined, then HOSTNAMES is computed by concatenating
# local host's actual name with each name in this colon-separated list of
# domain names.  This computation is done at run-time.
#
# Example: if DOMAINS="uts.amdahl.com:uucp", then the HOSTNAMES value
# for the site "amdahl" would become "amdahl.uts.amdahl.com:amdahl.uucp".

DOMAINS=uucp					# common
#DOMAINS=ussr.comm:uucp				# example only


# UUCP_NAME - name for the local host on the UUCP network
#
# optional
#
# This should be set to the name of the local host as known by the
# UUCP software.
#
# Normally, no value is given for this variable, in which case the
# value will be computed by smail at run-time from the actual name for
# local host, as computed in a system-dependent fashion.

#UUCP_NAME=kgbvax				# example only


# VISIBLE_NAME - local host name used in outgoing addresses
#
# optional
#
# Some installations may wish to hide a group of machines under a common
# name.  For example, at Amdahl, we may wish to hide the machines on our
# ethernet under the domain "uts.amdahl.com".  If we set the value
# VISIBLE_NAME="uts.amdahl.com" on the machine "futatsu", then mail
# from "futatsu" sent as if it came from "user@uts.amdahl.com" rather than
# "user@futatsu.uts.amdahl.com".  Of course, the "uts.amdahl.com" gateways
# will need to forward mail to "user", however the fact that a user
# does not have check for mail on all machines on the network is useful.
#
# The VISIBLE_NAME value will not be recognized as a name for the local
# host unless it is also included in one of the other lists of names for
# the local host.

#VISIBLE_NAME=kgbvax.uucp			# example only


# GATEWAY_NAMES - more names for the local host
#
# optional
#
# It is often important that hosts which are domain gateways recognize
# the domain names as alternate names for the local host.  These names
# should be defined in addition to those computed automatically from
# the actual name for the local host by putting them in GATEWAY_NAMES.
#
# This variable is a colon-separated list of names for the local host
# which is not computed from the actual name for the local host.

#GATEWAY_NAMES=moscow.ussr.comm:ussr.comm:comm	# example only


# POSTMASTER - the default address for the mail administrator
#
# This address is used by smail as a last resort in trying to deliver
# to the address "postmaster".  Normally, "postmaster" is aliased to a
# responsible person, or persons through the alias file.  In the event
# that no alias file exists, or that "postmaster" was not found in
# that file or by any other directors, the default address will be
# used.

POSTMASTER=root


# NOBODY - a user with few access capabilities
#
# optional
#
# The user named here will be used by smail whenever a user ID is
# desired that cannot do any more damange than any unpriveledged user
# on the system.  Under 4.3BSD and SunOS, this would be the user named
# "nobody".  Under other operating systems, it may be reasonable to
# create a "nobody" entry in the passwd file.  Some systems have a
# user such as "unknown" which will suffice.
#
# If this is not defined, then a default will be chosen.  This default
# is "nobody" for 4.3BSD and SunOS, and is otherwise "guest".

#NOBODY=nobody
#NOBODY=unknown			# we use this at amdahl.


# TEST_BASE - directory where smail test files are kept
#
# optional  (special when defined to an empty string)
#
# When testing smail, it is convenient to put binaries and configuration
# files in an area separated from the actual installation areas.  The
# TEST_BASE directory defines this alternate area.  Smail will assume
# assume a fixed hierarchy below this directory, with a "bin" subdirectory
# containing the smail binary and utilities, a "lib" directory containing
# smail configuration files, and a "spool" directory containing smail
# spool files.
#
# If no TEST_BASE is defined, then this facility is turned off.  If a
# TEST_BASE is defined to be an empty string, then all programs will be
# used in the area where they are compiled, LIB_DIR will be set to the
# "lib" directory under the root of the smail source tree, and SPOOL_DIRS
# will be set to the "spool" directory under the root of the smail source
# tree.  In this case, a "make install" is not required.
#
# If a TEST_BASE is defined as a relative path (e.g. "."), then it is
# defined relative to the root of the smail source directory.

#TEST_BASE=/usr/project/smail
#TEST_BASE=test
#TEST_BASE=					# use progs in source area


# SMAIL_BIN_DIR - directory where copies of the smail binary are kept
#
# The Smail program comes in user callable names: smail, uupath,
# pathto, optto, and so on.  A copy of smail will be linked to files
# under SMAIL_BIN_DIR.  The SMAIL_BIN_DIR should be a directory
# that is commonly in users search path (i.e., $PATH).

SMAIL_BIN_DIR=/usr/local			# BSD local convention
#SMAIL_BIN_DIR=/usr/amdahl/bin			# convention for UTS/580
#SMAIL_BIN_DIR=/usr/lbin			# Sys V local convention
#SMAIL_BIN_DIR=/usr/local/bin			# yet another tradition
#SMAIL_BIN_DIR=/usr/smail/bin			# I use this right now


# SMAIL_NAME - file where the primary working copy of smail is located
#
# optional
#
# Any program that needs to call smail, including smail itself will
# attempt to execute the program named by SMAIL_NAME.
#
# Often the primary working copy of smail is /usr/lib/sendmail.  This
# should be used for systems that used to run sendmail.  Programs such
# as Berkeley Mail, System V mailx or /bin/mail can be made to, or do
# call /usr/lib/sendmail for mailer activity.  It is common for public
# domain programs to expect a mailer to exist under this name, also.
#
# If SMAIL_NAME is not defined here, or is set to a null string, then
# $SMAIL_BIN_DIR/smail is used instead.  If this is the name that you
# want to use as the primary binary pathname, then do set SMAIL_NAME
# to the null string.  This will prevent the smail src/Makefile from
# installing it as $SMAIL_BIN_DIR/smail twice.

SMAIL_NAME=/usr/lib/sendmail			# common convention
#SMAIL_NAME=					# use smail in bin directory


# OTHER_SMAIL_NAMES - other names under which to install smail
#
# optional
#
# Many systems will wish to install smail as /bin/rmail to catch mail
# coming in over UUCP directly with smail.  To install under this
# name set OTHER_SMAIL_NAMES to /bin/rmail.  As implied by the name,
# other pathnames can be specified as well, if a system has other
# potential rendezvous points for mail.  This should be a colon or
# white-space separated list of full pathnames.
#
# This is assumed to be empty when TEST_DIR is defined.

OTHER_SMAIL_NAMES=/bin/rmail			# common
#OTHER_SMAIL_NAMES=/usr/lib/sendmail		# could use this rather
						# than putting it into
						# SMAIL_NAME


# LIB_DIR - directory where various smail files are found
#
# The LIB_DIR is where various static smail files reside, by default.
# Files which may reside under this directory are: the primary config
# file, the directors, routers and transports files, an aliases file,
# pathalias database, uuwho database, and the COPYING file.
#
# The common subdirectories under LIB_DIR are: "methods", where method
# files are by default found; "maps", where local pathalias files,
# mkmap configuration files and the getmap batch file is located;
# and "lists" where mailing lists are commonly located.
#
# It should be noted that none of these files, except for COPYING,
# is required by the smail binary as it is released.  See smail(5)
# and smail(8) for more details on this and related topics.

LIB_DIR=/usr/lib/smail				# common convention
#LIB_DIR=/usr/local/lib/smail
#LIB_DIR=/usr/smail/lib				# I use this right now


# UTIL_BIN_DIR - directory where smail utilities are located
#
# The smail system has a number of programs such as pathalias, mkline,
# mksort, mkdbm that users normally need not execute directly.  Such
# utilities will be placed under the UTIL_BIN_DIR directory.
#
# UTIL_BIN_DIR is often the same as LIB_DIR.

UTIL_BIN_DIR=$LIB_DIR				# common, same as LIB_DIR
#UTIL_BIN_DIR=/usr/smail/util			# I use this right now


# NEWALIASES - alternate pathname for mkaliases program
#
# optional
#
# For compatibility with sendmail, mkaliases can be installed under
# a name such as /usr/ucb/newaliases, or /usr/lib/newaliases.  To setup
# smail to perform this installation, set NEWALIASES to the desired full
# pathname.  When testing, this is set to the empty string, signifying
# that mkaliases will be installed only under the name mkaliases.

#NEWALIASES=$UTIL_BIN_DIR/newaliases
#NEWALIASES=/usr/local/bin/newaliases
NEWALIASES=/usr/ucb/newaliases			# BSD location
#NEWALIASES=/usr/lib/newaliases			# UTS/580 location


# SECOND_CONFIG_FILE - pathname of an alternate config file
#
# optional
#
# Smail allows one to have a second set of configuration files that can
# override both the compiled in and the optional primary config file.
# Normally, the path to this secondary configuration file is defined
# in the primary smail configuration file.  However the value
# SECOND_CONFIG_FILE can be the filename of the secondary (alternate)
# config file.  In the case where both this value, and where the
# LIB_DIR/config file specifies a "second_config_file" value, the
# LIB_DIR/config file takes presidence.
#
# A secondary configuration file is useful in an environment with
# distributed filesystems.  In such an environment, the regular config
# directory can be maintained centrally on a remotely mounted
# filesystem.  Individual machines, can then setup a secondary
# configuration file which overrides these centrally maintained files
# for specific purposes.

# For example, in a network with one gateway to the outside world,
# all could share the same smail binaries and standard configuration.
# However the the gateway machine could have a secondary configuration
# file which so that the gateway's the smail setup has greater intelligence
# and thus act as a smart_user and smart_path host.

SECOND_CONFIG_FILE=				# common for non-NFS systems
#SECOND_CONFIG_FILE=/private/usr/lib/smail	# convention for NFS systems


# PATHS_FILE, PATHS_TYPE - location and type of the paths database
#
# optional
#
# If PATH_FILE begins with a '/', then it is the name of the optional
# pathalias database, otherwise it is assumed that PATH_FILE refers to
# a file under the LIB_DIR directory.
#
# For use with YP, it may be more convenient to use the "yp" type,
# rather than "aliasyp", because this way a paths file can be maintained
# in a format compatible with other YP maps.
#
# Caution, if the dbm(3x) library is available, yet the 4.3BSD ndbm(3)
# routines are not, then only one dbm file can be used by smail.  Thus,
# in this case either, but not both, of the PATHS_FILE and ALIASES_FILE
# can be in dbm format.
#
# If PATHS_FILE is left undefined, no paths file is defined in the
# preloaded smail configuration.

PATHS_FILE=paths				# for file under LIB_DIR
#PATHS_FILE=mail.paths				# for use over Sun YP

#PATHS_TYPE=dbm					# for sites with dbm or ndbm
PATHS_TYPE=bsearch				# for sorted files, faster
#PATHS_TYPE=lsearch				# linear search
#PATHS_TYPE=yp					# for use over Syn YP

# ALIASES_FILE, ALIASES_TYPE - location and type of the aliases database
#
# optional
#
# If ALIASES_FILE begins with a '/', then it is the full pathname of the
# optional aliases database, otherwise it is assumed that ALIASES_FILE
# refers to a file under the LIB_DIR directory.
#
# For use with YP, it may be more convenient to use the "yp" type,
# rather than "aliasyp", because this way a paths file can be maintained
# in a format compatible with other YP maps.
#
# NOTE:	 If ALIASES_TYPE is specified as bsearch, then the suffix .sort
#	 will be appended to the filename given in ALIASES_FILE.  The
#	 mkaliases command will then treat a file without that suffix
#	 as the unsorted source file for the database.
#
# Caution, if the dbm(3x) library is available, yet the 4.3BSD ndbm(3)
# routines are not, then only one dbm file can be used by smail.  Thus,
# in this case either, but not both, of the PATHS_FILE and ALIASES_FILE
# can be in dbm format.
#
# If ALIASES_FILE is left undefined, no aliases file is defined in the
# preloaded smail configuration.

ALIASES_FILE=/usr/lib/aliases			# compatible with sendmail
#ALIASES_FILE=aliases				# for file under LIB_DIR
#ALIASES_FILE=mail.aliases			# for use over Sun YP

#ALIASES_TYPE=dbm				# compatible with sendmail
ALIASES_TYPE=lsearch				# for sites without dbm(3x)
#ALIASES_TYPE=bsearch				# for sorted files, faster
#ALIASES_TYPE=aliasyp				# for use over Sun YP


# UUCP_SYSTEM_FILE - path to UUCP file containing remote systems
#
# optional
#
# The normal smail configuration defines a router that scans the
# output of the /usr/bin/uuname command for neighboring UUCP sites.
# When smail is running as a daemon, it can cache the output of uuname
# so that the uuname command need not be executed for each mail
# message.  In order to be able to detect when the output of uuname
# will change, smail daemons will stat the UUCP configuration file
# which contains the names of neighboring hosts.  This EDITME variable
# defines the full pathname to this file.  If this variable is not
# defined, then the output of the uuname will not be cached.

#UUCP_SYSTEM_FILE=/usr/lib/uucp/L.sys		# use this for normal UUCP
#UUCP_SYSTEM_FILE=/usr/lib/uucp/Systems		# use this for HoneyDanBer UUCP


# SPOOL_DIRS - smail spooling directories
#
# Smail can use one or more spooling directories, where spool directories
# other than the first are used if earlier spool directories were
# inaccessible or were on file systems which filled up.  The list of spool
# directories should be colon-separated and may contain only one spool
# directory if desired.

SPOOL_DIRS=/usr/spool/smail			# common
#SPOOL_DIRS=/usr/spool/smail:/usr2/spool/smail	# use of alternate filesystem
#SPOOL_DIRS=/usr/smail/spool			# I use this right now


# UNSHAR_MAP_DIR - where unshared USENET map files are to be placed
#
# optional
#
# The getmap utility will read a list of files on the file
# LIB_DIR/map/batch, and using unsharmap unshar these maps into the
# UNSHAR_MAP_DIR directory.
#
# A common way that maps are distributed is through the USENET news group
# "comp.mail.maps".  A sys file line of:
#
#	usenet-maps:comp.mail.maps,world:F:<LIB_DIR>/map/batch
#
# where <LIB_DIR> is the value of LIB_DIR above, will add names into
# the LIB_DIR/map/batch file for getmap to process.
#
# If the UNSHAR_MAP_DIR is not defined, then getmap and uuwho utilities
# will not function.

UNSHAR_MAP_DIR=/usr/spool/uumaps


# TMP_DIR - secure temp directory used by smail utilities
#
# Some smail utilities use TMP_DIR to define a directory in which
# their temporary files can be created.  Utilities that use this
# directory are those that wish to use a secure temporary area.
#
# The only smail utilities that need to use TMP_DIR are utilities that
# should be run as root, or as some other user with appropriate privledges.  
# It is therefore recommended that TMP_DIR not be globally writable.  

TMP_DIR=$UNSHAR_MAP_DIR/tmp			# common
#TMP_DIR=/usr/tmp				# if /usr/tmp is sticky
#TMP_DIR=$LIB_DIR/tmp				
#TMP_DIR=/usr/local/lib/smail/tmp


# SECURE_PATH - path for smail utilities
#
# The smail utilities often set their PATH to begin with the SECURE_PATH.
# The SECURE_PATH should be a path of directories where standard commands
# are located.  These directories and commands should not be writeable by
# normal users.  A common directory for smail utilities to append to
# SECURE_PATH is UTIL_BIN_DIR.

SECURE_PATH=/bin:/usr/bin:/usr/ucb		# common for BSD systems
#SECURE_PATH=/bin:/usr/bin:/usr/amdahl/bin	# common for UTS/580 systems
#SECURE_PATH=/bin:/usr/bin			# common for System V system


# GROK_VOID - Define this to "yes" if the void type is fully supported
#
# Many systems support the void type but do not support initialized
# values which are pointers to functions which return void.  Test for this
# with the program fragment:
#	void f();
#	void (*avf[])() = { f };
# If this produces an error from your compiler, do not define GROK_VOID.

GROK_VOID=yes					# use this if void works
#GROK_VOID=					# otherwise, use this


# MAN1 - where smail user command man pages are to be installed
# MAN5 - where smail file format man pages are to be installed
# MAN8 - where smail administrator man pages should be installed
# MAN1_EXT - file extension for user command man pages
# MAN5_EXT - file extension for file format man pages
# MAN8_EXT - file extension for adminstrator man pages
#
# optional
#
# The man page for "foo.an" in the smail man/man5 source directory
# will be installed in MAN5/foo.MAN5_EXT, if MAN5 is defined.
#
# For some reason, BSD and System V differ on where file format man
# pages are kept, hence the unusual values of MAN5 for System V.

MAN1=/usr/man/man1				# common for BSD systems
#MAN1=/usr/man/u_man/man1			# common for System V systems
#MAN1=/usr/local/man/man1			# common for local man pages
MAN1_EXT=1					# common

MAN5=/usr/man/man5				# common for BSD systems
#MAN5=/usr/man/a_man/man4			# common for System V systems
#MAN5=/usr/local/man/man5			# common for local man pages
MAN5_EXT=5					# common for BSD systems
#MAN5_EXT=4					# common for System V systems

MAN8=/usr/man/man8				# common for BSD systems
#MAN8=/usr/man/a_man/man8			# common for System V systems
#MAN8=/usr/local/man/man8			# common for local man pages
MAN8_EXT=8					# common


# COMPRESS - file compression
#
# The savelog utility can save space by compressing old log files.
# Normally when a file is compressed, the suffix is added to the
# filename.
#
# The COMPRESS symbol is the name of a program such that:
#
#		$COMPRESS $COMP_FLAG filename ...
#
# the file: filename is replaced by: filename$DOT_Z
# regardless of the size of filename.  The command:
#
#		$UNCOMPRESS filename$DOT_Z
#
# will replace filename$DOT_Z with the original filename.
# The command:
#		$ZCAT filename$DOT_Z
#
# will read the compressed file: filename$DOT_Z and write the
# plain text to standard output while leaving the file compressed.

COMPRESS=compress				# common
COMP_FLAG="-f"
UNCOMPRESS=uncompress
ZCAT=zcat
DOT_Z=".Z"

#COMPRESS=pack					# System V standard
#COMP_FLAG="-f"
#UNCOMPRESS=unpack
#ZCAT=pcat
#DOT_Z=".z"

#COMPRESS=true					# if no compress is used
#COMP_FLAG=""
#UNCOMPRESS=true
#ZCAT=cat
#DOT_Z=""


# LMAIL - where the real /bin/mail resides
#
# optional
#
# One many System V machines, the /bin/mail program will deliver what 
# it thinks is local mail directly into user mailboxes.  The /bin/mail
# program will therefore can bypass all aliasing does by Smail.  
#
# A solution to this program is to move this /bin/mail to LMAIL and
# install binmail as /bin/mail.  If binmail is invoked to read mail, 
# the LMAIL (old /bin/mail) is called, otherwise SMAIL is called
# to deliver mail.
#
# If LMAIL defined below and the file LMAIL does not exist, then the binmail 
# makefile install rule will attempt to move /bin/mail to LMAIL and then 
# copy binmail into /bin/mail.  If LMAIL is defined and the file LMAIL
# does not exist, then the binmail makefile will refuse to install binmail.
#
# If LMAIL is not defined then /bin/mail is not touched.
#
# NOTE: due to potential problems with binmail installation, binmail
#	is not automatically built and installed from higher level
#	makefiles.  One must go to the pd/binmail directory directly
#	and make install it 'by hand'.

#LMAIL=/bin/lmail				# standard System V


# MISC_C_DEFINES - miscellaneous #defines for C programs
# MISC_C_DEFINES - miscellaneous #defines for C programs
#
# optional
#
# The value of MISC_C_DEFINES is included directly into the file defs.h
# in each source directory.  It is useful as a central place for
# miscellaneous #defines not otherwise setable above.  In particular,
# it is useful for overriding other more values given in the file
# src/config.h.  It was felt that it was appropriate to keep the
# EDITME file fairly small, with only a reasonable subset of the
# configurable aspects of smail being explicitly described.  As a
# result, there may be some other things in config.h that you may
# wish to change.  Use #define's here to accomplish this.
#
# A suitable collection of #undef's and #define's here can also
# change the behavior defined in the file under conf/os or conf/arch
# for your operating system and architecture.  However, use of
# MISC_C_DEFINES for this is discouraged.
#
# As with /bin/sh scripts, a logical line beginning with a : causes
# that line to be parsed but ignored.  If it were simply commented out
# then the second line would be processed.

: MISC_C_DEFINES='			/* example only */
#undef ALIASES_FILE
#define NO_ALIASES_FILE			/* disable aliases file */
#define REQUIRE_CONFIGS TRUE		/* dont allow optional config files */
#define DIRECTOR_FILE NULL		/* no director file */
#define TRANSPORT_FILE NULL		/* no transport file */
#undef LOCAL_MAIL_FILE			/* see src/config.h */
#define LOCAL_MAIL_FILE "/usr/mail/${lc:user}"
'


# MISC_SH_DEFINES - miscellaneous script to include in defs.sh
#
# The value of MISC_SH_DEFINES is included directly into the file
# defs.sh, in each source directory.  It is a useful place to store
# script lines to override values set by the mkdefs.sh shell script
# or in a conf/os or conf/arch file.
#
# As with /bin/sh scripts, a logical line beginning with a : causes
# that line to be parsed but ignored.  If it were simply commented out
# then the second line would be processed.

: MISC_SH_DEFINES='			# example only
LIST_FILENAME="~operator/mail/lists/${lc:user}"	# somewhat silly example
LIBS="$LIBS -ldirect"			# more useful example
'


# MISC_SED_DEFINES - miscellaneous lines to include in defs.sed
#
# The value of MISC_SED_DEFINES is included directly into the file
# defs.sed, in each source directory.  It is a useful place to store
# sed lines to override lines set by the mkdefs.sh shell script from
# information in a conf/os or conf/arch file.
#
# As with /bin/sh scripts, a logical line beginning with a : causes
# that line to be parsed but ignored.  If it were simply commented out
# then the second line would be processed.

# We can't readily think of good examples for this one.
: MISC_SED_DEFINES=''