#! /bin/sh
#
# @(#)setLPSDOC	1.2	LPS_UNX_COM	2/19/95
#
# Copyright 1995   Digital Equipment Corporation, Maynard, MA
#
# setLPSDOC
#
# A script that produces a value for attribute LPSDOC.
#
# Parameters:
#    $1 - LPS class identifier, one of {PC, MC, PS, ENV}
#    $2 - Operating system type identifier (eg: SV2, BSD, etc)
#    $3 - Print client type identifier (eg: AIX, BSD, SV3, etc)
#    $4 - PrintServer printer model (eg: LPS17, LPS20)
#    $5 - Default value for the attribute
#    $6 - Path of the output file to receive the final attribute value
#
# Global variables:
#    ECHON
#    FUNCS
#    PAGER
#    TMPDIR
#
# Exit values:
#    0 - Success, output file contains newly set attribute value.
#    1 - Error or interruption occurred, error messages go to stderr,
#	 contents of the output file are undefined.
###

CLASS=$1
OSTYPE=$2
PCTYPE=$3
PSMODEL=$4
DEFVAL=$5
OUTFILE=$6

. $FUNCS   # Import the standard LPS shell functions

showhelp true "
In what directory should LPS documentation files reside?

Several text and PostScript(R) files come with the LPS software kit
describing various aspects of the PrintServer system.  Most of these
documentation files are for use by system managers and other personnel
responsible for the operation of the LPS software.  However, there are
some user-level documentation files you may wish to distribute to your
user community.

Note carefully that these documentation files do NOT include the many
online manual pages for use with the man(1) command.  The manual pages
are handled separately from these documentation files and are
typically copied into the standard \"/usr/man\" directory tree during
installation.

Typically a site will choose the default response, in which case you
should simply press the RETURN key when the question is asked."

getpath d "$DEFVAL" "LPS documentation files directory"

if [ -z "$RESPONSE" ]
then
    RESPONSE="$DEFVAL"
fi

echo "$RESPONSE" > $OUTFILE

exit 0
