/[cvs]/eggdrop1.9/doc/patch.howto
ViewVC logotype

Contents of /eggdrop1.9/doc/patch.howto

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.10 - (show annotations) (download)
Sun Feb 23 09:52:46 2003 UTC (16 years, 1 month ago) by wcc
Branch: MAIN
CVS Tags: HEAD
Changes since 1.9: +0 -0 lines
FILE REMOVED
* More docs.

1 PATCH HOWTO v1.2 29 May 2000
2
3
4
5 INDEX
6
7 I. ABOUT THIS DOCUMENT
8 II. TERMS USED
9 III. APPLYING A PATCH
10 IV. DOING AND SUBMITTING PATCH
11 V. DOWNLOADING A PATCH
12
13
14
15
16
17
18 I. ABOUT THIS DOCUMENT
19
20 The purpose of this document is to show you what a patch is and how you
21 can apply a patch.
22
23
24
25
26
27 II. TERMS USED
28
29 The following are some common terms used in this document.
30 If applicable, there is also the associated command named.
31
32
33 patch
34 A patch is an update for a sourcecode of a program (here eggdrop). Be
35 carefull, every patch is designed for a speciall eggdrop version and
36 cannot be applied on every bot!
37
38
39
40
41
42 III. APPLYING A PATCH
43
44 To apply a patch to an eggdrop you have to get first the sourcecode of
45 it (you should always keep a tar.gz archieve with the source of your
46 current eggdrop on your shell). In the next step you have to change to
47 your current source directory (i.e.: /home/user/eggdrop1.7.0/) and type
48 the following command:
49
50 patch -p1 < ../path.to.the/patch
51
52 Once this is complete, execute the following command:
53
54 find . -name "*.rej" -print
55
56 If it returns a list with filenames ending with .rej extension then the
57 patch didn't apply properly. Ensure that the patch is intended for your
58 version and that you have the original source. You should also try to
59 re-download the patch to ensure, that the patch is not corrupted.
60
61 If the patch applied properly the only thing left to do is to recompile
62 your eggdrop and install the new modules and binaries.
63
64
65
66
67
68 IV. DOING AND SUBMITTING PATCH
69
70 If you fixed a bug and changed something in eggdrop's source code it would
71 be really nice to let the dev team know about it, so they can apply it to next
72 eggdrop release.
73 There are several steps to submit a patch to the eggdev team:
74
75 1. make a directory with orig. source tree and one with modified source tree
76 2. do a 'diff -bur eggdrop1.7.original eggdrop1.7.modified > myfirst.patch'
77 3. send an email to patches@eggheads.org with the patch attached and a detailed
78 description of what you changed and why you changed it. Don't forget to write
79 for which botversion your patch was made. Please send a second email with
80 same info to eggdev@eggheads.org, this time without the patch attached.
81
82
83 Please, never patch src/patch.h or one of the UPDATES files. We will do it.
84 Thank you.
85
86
87
88
89
90 V. DOWNLOADING A PATCH
91
92 All patches for eggdrop1.7.x can be found on ftp.eggheads.org in
93 /pub/eggdrop/patches/1.7
94
95
96
97 Hope that this document helped you in some way...

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23