1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
APPLYING PATCHES
To apply a package, first make sure you have the original source
that the patch was intended for. Change into that directory, than use
the following command:
gunzip -c {full_path_of_patch} | patch -p1
-or-
gzip -dc {full_path_of_patch} | patch -p1
Note: if the patch does NOT have a ".gz" suffix, use this instead:
patch -p1 < {full_path_of_patch}
It should create NO *.rej files. If it does, then something
didn't work right. If applying to a different base than the patch was
intended for, patch may create *.orig files. These are usually OK, just
make sure no *.rej files were created.
SUBMITTING PATCHES
All patches should be sent to me:
Insomnia (Stea Greene) <insomnia@core.binghamton.edu>
Make sure to send a full, detailed description of what your patch
does, what it changes and what it fixes.
To create a patch, first make sure you have a full tree of both
the original and the modified trees (herin called "gatos-orig" and
"gatos-new" respectively). Make sure each tree is clean by using:
make distclean
in EACH directory. Then change to the directory immediately
above these two directories and use the following command.
diff -ur gatos-orig gatos-new > gatos-new-patch
Look at gatos-new-patch (with a text editor or viewer) and make
sure nothing is changed that you didn't intend to be. You can submit
this patch to me either included in an e-mail, or as a MIME attachment,
or you can compress it and send it as a MIME attachment, as follows:
Compress it with:
gzip -9 gatos-new-patch
Then send gatos-new-patch.gz to me as a MIME attachment.
If there is a problem with the patch, or I have a question or the
patch/description is not understood, you will get a reply, so make sure
your message is properly reply-able.
|
