![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to README CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / patch|
Return to README CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / patch |
1.1 root 1:
2: The Makefile and config.h files in this directory work with the current
3: BSD release. Don't run the Configure script, you'll get wrong results.
4:
5: Keith Bostic 1/10/88
6: -----------------------------------------------------------------------------
7:
8: Patch Kit, Version 2.0
9:
10: Copyright (c) 1986, Larry Wall
11:
12: You may copy the patch kit in whole or in part as long as you don't try to
13: make money off it, or pretend that you wrote it.
14: --------------------------------------------------------------------------
15:
16: Please read all the directions below before you proceed any further, and
17: then follow them carefully. Failure to do so may void your warranty. :-)
18:
19: After you have unpacked your kit, you should have all the files listed
20: in MANIFEST.
21:
22: Installation
23:
24: 1) Run Configure. This will figure out various things about your system.
25: Some things Configure will figure out for itself, other things it will
26: ask you about. It will then proceed to make config.h, config.sh, and
27: Makefile.
28:
29: You might possibly have to trim # comments from the front of Configure
30: if your sh doesn't handle them, but all other # comments will be taken
31: care of.
32:
33: If you don't have sh, you'll have to rip the prototype of config.h out
34: of Configure and generate the defines by hand.
35:
36: 2) Glance through config.h to make sure system dependencies are correct.
37: Most of them should have been taken care of by running the Configure script.
38:
39: If you have any additional changes to make to the C definitions, they
40: can be done in the Makefile, or in config.h. Bear in mind that they may
41: get undone next time you run Configure.
42:
43: 3) make
44:
45: This will attempt to make patch in the current directory.
46:
47: 4) make install
48:
49: This will put patch into a public directory (normally /usr/local/bin).
50: It will also try to put the man pages in a reasonable place. It will not
51: nroff the man page, however.
52:
53: 5) Read the manual entry before running patch.
54:
55: 6) IMPORTANT! Help save the world! Communicate any problems and
56: suggested patches to me, [email protected] (Larry Wall), so we can
57: keep the world in sync. If you have a problem, there's someone else
58: out there who either has had or will have the same problem.
59:
60: If possible, send in patches such that the patch program will apply them.
61: Context diffs are the best, then normal diffs. Don't send ed scripts--
62: I've probably changed my copy since the version you have.
63:
64: Watch for patch patches in net.sources.bugs. Patches will generally be
65: in a form usable by the patch program. If you are just now bringing up
66: patch and aren't sure how many patches there are, write to me and I'll
67: send any you don't have. Your current patch level is shown in patchlevel.h.
68:
69:
70: NEW FEATURES IN THIS RELEASE
71:
72: (Correct) support for 4.3bsd-style context diffs.
73: Files can be created from scratch.
74: You can specify a fuzz-factor for context matching.
75: You can force patch to ask no questions.
76: You can specify how much of the leading pathname to strip off filenames.
77: Uses a Configure script for greater portability.
78: You are now asked if you want to apply a reversed patch.
79: No limit (apart from memory) on the size of hunks.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.