|
|
1.1 root 1: Warp Kit, Version 7.0
2:
3: Copyright (c) 1986, Larry Wall
4:
5: You may copy the warp kit in whole or in part as long as you don't try to
6: make money off it, or pretend that you wrote it.
7: --------------------------------------------------------------------------
8:
9: Warp is a real-time space war game that doesn't get boring very quickly.
10: Read warp.doc and the manual page for more information.
11:
12: Warp will probably not run on V7 systems that don't have a non-blocking read,
13: or on machines with a small address space like the PDP-11. Caveat Emptor.
14:
15: Please read all the directions below before you proceed any further, and
16: then follow them carefully. Failure to do so may void your warranty. :-)
17:
18: After you have unpacked your kit, you should have all the files listed
19: in MANIFEST.
20:
21: IMPORTANT
22:
23: You must choose the uid that you want warp to run under, since warp runs
24: setuid to protect its files. Choose a uid (not root) that is used only
25: by trustworthy persons. If you do your make install as root, the installed
26: version will be chowned to this uid. Otherwise, you should login to your
27: selected uid before proceeding. The Configure script will ask you which
28: uid you want warp to run under.
29:
30: Installation
31:
32: 1) Run Configure. This will figure out various things about your system.
33: Some things Configure will figure out for itself, other things it will
34: ask you about. It will then proceed to make config.h, config.sh, and
35: Makefile.
36:
37: You might possibly have to trim # comments from the front of Configure
38: if your sh doesn't handle them, but all other # comments will be taken
39: care of.
40:
41: (If you don't have sh, you'll have to copy the sample file config.H to
42: config.h and edit the config.h to reflect your system's peculiarities.)
43:
44: 2) Glance through config.h to make sure system dependencies are correct.
45: Most of them should have been taken care of by running the Configure script.
46:
47: If you have any additional changes to make to the C definitions, they
48: can be done in the Makefile, or in config.h. Bear in mind that they will
49: get undone next time you run Configure.
50:
51: 3) make depend
52:
53: This will look for all the includes and modify Makefile accordingly.
54: Configure will offer to do this for you.
55:
56: 4) make
57:
58: This will attempt to make warp in the current directory.
59:
60: 5) make install
61:
62: This will put warp into a public directory (normally /usr/games).
63: It will also try to put the man pages in a reasonable place. It will not
64: nroff the man page, however. You may need to be root to do this. If
65: you are not root, you must own the directories in question and you should
66: ignore any messages about chown not working.
67:
68: 6) Read the manual entry before running warp.
69:
70: 7) Feel free to edit warp.news.
71:
72: 8) IMPORTANT! Help save the world! Communicate any problems and
73: suggested patches to me, [email protected] (Larry Wall), so we can
74: keep the world in sync. If you have a problem, there's someone else
75: out there who either has had or will have the same problem.
76:
77: If possible, send in patches such that the patch program will apply them.
78: Context diffs are the best, then normal diffs. Don't send ed scripts--
79: I've probably changed my copy since the version you have.
80:
81: Watch for warp patches in comp.sources.bugs. Patches will generally be
82: in a form usable by the patch program. If you are just now bringing up
83: warp and aren't sure how many patches there are, write to me and I'll
84: send any you don't have. Your current patch level is shown in patchlevel.h.
85:
86:
87: NEW FEATURES IN THIS RELEASE
88:
89: Uses a Configure script for greater portability.
90: Space Amoebas!!!
91: Pirates
92: Friendly Freighters
93: Harry Mudd
94: Damage
95: Keyboard mapping
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.