Newsgroups: comp.sources.d
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!uunet!sparky!kent
From: kent@sparky.IMD.Sterling.COM (Kent Landfield)
Subject: Help define Environment: usage in c.s.m
Message-ID: <1991May26.041741.22210@sparky.IMD.Sterling.COM>
Sender: kent@sparky.IMD.Sterling.COM (Kent Landfield)
Organization: Sterling Software, IMD
Date: Sun, 26 May 1991 04:17:41 GMT
Lines: 124

Its time to get serious about this.   I *need* your input.  Please jump in 
with suggestions and ideas. 

The Environment: auxilary header will be used in the comp.sources.misc 
newsgroup in the very near future. 

Why is this being added ? 

    I have been shown that in a newsgroup not restricted to one type of
    operating system, one type of machine or one type of architecture that 
    there is a need for this type of information in the header.  The intent
    is to provide you more external information about the package contained 
    within the posting.  This allows you to determine if the package has 
    special requirements that may prevent you from using it.  It is extremely 
    irritating to take the time to unpack something just to find out that you 
    can't use it.
    
The Environment: auxiliary header is currently in use in comp.sources.games.  
What follows is a description of the Environment: header as Bill has been 
using it. It seems quite reasonable so... :-)

    The Environment: auxiliary header line is used to allow the moderators
    a way of giving the readership a quick indication of what resources are 
    required to use a particular issue.

    Environment: syntax
        Environment: Keyword [, keyword ..]

    Environment: example
        Environment: SunView, XView, X11R4, termcap

    The keywords usage is case insensitive.  I am extending Bill's usage 
    by adding a NOT indicator (e.g. !AIX) so that I can specify that a 
    package runs on everything "but" the specified keyword.

Now here is the part where I need your help...

 1. When should the Environment: header be used ? Always or just when the 
    moderator is alerted to a limiting condition ?  Something in between ?  

 2. The environment information could get quite lengthy for some packages,
    perl comes to mind... :-)  Would it be acceptable to have more than
    one line of Environment: headers if needed ?

 3. A set of Keywords needs to be generated. The following list of keywords
    is used only as a starting pont for discussion.  *Much* help is needed 
    here.  This was a quick and dirty list so suggest additions and changes...

        Keyword                   Meaning
        -------              ----------------------------
Operating Systems:
        UNIX         -      Will operate on any unix system... (right...)
	SYSV         -      Will operate on any System 5.0 or greater system.
	SYSV2        -      Will operate on any System 5.2
	SYSV4        -      Will operate on any System 5.4
	BSD          -      Will operate on any version of BSD
	BSD42        -      Will operate on BSD 4.2
	BSD43        -      Will operate on BSD 4.3
	SUNOS        -      Will operate on Sun OS
	SUNOS4.1     -      Will operate on Sun OS 4.1
	ULTRIX       -      Will operate on Ultrix 
	AIX          -      Will operate on AIX 
	VMS          -      Will operate on VMS
	MSDOS        -      Will operate on MSDOS 
	XENIX        -      Will operate on Xenix
	MINIX        -      Will operate on Minix
	MACOS        -      Will operate on Macintosh OS
	AMIGA        -      Will operate on AMIGA OS
	COHERENT     -      Will operate on Mark Williams Coherent OS
	OS/2         -      Will operate on half an OS

Window Environments:
        Curses       -      Uses the curses library
        Termcap      -      Uses the termcap library
	SunView      -      Uses Sunview windowing Facilities
	X11          -      Uses X Windows 
	X11R3        -      Uses X Windows Release 11.3
	X11R4        -      Uses X Windows Release 11.4
	XView        -      Uses XView toolkit
	Motif        -      Uses Motif toolkit
	XVT          -      Uses XVT toolkit
        (There is a few more that go here... )

System/Language Support:  (C is the default so not specified)
        Dirent       -      Uses the dirent directory access routines
        Sockets      -      Uses the network socket library
	RPC          -      Remote Procedure Call facilities
	ANSI-C       -      Requires ANSI C compiler
	Turbo-C      -      Requires Turbo C
	Pascal       -      Written in Pascal
	Fortran      -      Written in Fortran
	Perl         -      Written in Perl
	Lisp         -      Written in Lisp
        yacc         -      Requires yacc/bison
        lex          -      Uses lex
	MSGQ         -      Uses System V Message Queues
	SHM          -      Uses System V Shared Memory

Shell Support:     (sh is the default so not specified)
	CSH          -      C Shell required
	KSH          -      Korn Shell required
	BASH         -      Bash Shell required
	ZSH          -      Z Shell required
	RC           -      Plan 9 Shell required

Hardware Support:
	PC           -      IBM PC or compatible
	VGA          -      VGA video support needed
	EGA          -      EGA video support needed
	            
Architecture: sparc, risc, vax .. ??

There are many things missing from this list...  I am hoping we can 
come up with good definition of how the Environment: header is to be 
used and a set of keywords to use with it.  

Your turn...  

			-Kent+
-- 
Kent Landfield                   INTERNET: kent@sparky.IMD.Sterling.COM
Sterling Software, IMD           UUCP:     uunet!sparky!kent
Phone:    (402) 291-8300         FAX:      (402) 291-4362
Please send comp.sources.misc-related mail to kent@uunet.uu.net.