|
Sender: |
Revised LISTSERV forum <LSTSRV-L@DEARN> |
Subject: |
|
From: |
Ross Patterson <A024012@RUTVM1> |
Date: |
Thu, 4 Feb 88 08:58:04 EST |
In-Reply-To: |
Message of Thu, 4 Feb 88 12:41:31 SET from <REICHETZ@AWIIMC11> |
Comments: |
Warning -- original Sender: tag was LSTSRV-L@FRECP11 |
Reply-To: |
Revised LISTSERV forum <LSTSRV-L@DEARN> |
Nested packages are an important feature of the LISTSERV File
Server. But you should specify them as "<fn> PACKAGE <filelist>", not
as "<fn> $PACKAGE <filelist>". Remember, the $PACKAGE file contains
the list of files that comprise the package. The PACKAGE file doesn't
actually exist, its availability is implied by the existance of a
$PACKAGE file.
For example, assume a package called "SYSTEM", available through
the "JUNK" filelist, and comprised of three sections: "USERCODE",
"DVMCODE", and "MANUALS" (every system needs manuals, right?). You
might build the packages as follows:
File: SYSTEM $PACKAGE
* This file is the full SYSTEM package
USERCODE PACKAGE JUNK Package of User Interface code
DVMCODE PACKAGE JUNK Package of Disconnected VM code
MANUALS PACKAGE JUNK Package of Documentation (incomplete)
INSTALL LISTING JUNK Installation instructions
*
* The SYSTEM system is copyright 1999 by XYZ Computer Corp.
File: USERCODE $PACKAGE
* This file is the User Interface to the SYSTEM system
SMSG ASSEMBLE JUNK Source for SMSG command
SMSG HELPSYST JUNK Help for SMSG command
*SMSG DOCUMENT JUNK User Manual (not ready yet - sorry)
File: DVMCODE $PACKAGE
* This file is the Server for the SYSTEM system
LOOPER ASSEMBLE JUNK Source for the main server module
WAITER ASSEMBLE JUNK Source for working routine #1
Users GETing or AFDing to "SYSTEM PACKAGE" would receive all
files, while those GETing or AFDing to "USERCODE PACKAGE" would only
receive the user interface files.
Ross Patterson
Rutgers University
|
|
|