1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
2
<!-- $Id: patch-howto.html,v 1.3 2004/01/09 05:56:36 wcc Exp $ -->
6
<title>Eggdrop Documentation: Patch Howto</title>
11
<p><strong>Patch Howto</strong></p>
15
<p>The purpose of this document is to show you what a botnet is and how
16
it could be useful to you. It also covers botflags userfile sharing.</p>
19
<p><strong>Contents</strong></p>
23
<li><a href="#sect1">Terms</a></li>
25
<li><a href="#sect2">Applying a patch</a></li>
27
<li><a href="#sect3">Creating and submitting a patch</a></li>
29
<li><a href="#sect4">Downloading a patch</a></li>
34
<p><a name="sect1"></a><strong>Terms</strong></p>
37
<p>The following are some common terms used in this document:</p>
40
<dt><strong>Patch</strong></dt>
43
<p>A patch is an update to the sourcecode of a program (here
44
Eggdrop). Be careful, every patch is designed for a special
45
Eggdrop version and cannot be applied on every bot!</p>
50
<p><a name="sect2"></a><strong>Applying a patch</strong></p>
52
<p>To apply a patch to an Eggdrop, you have to first obtain the Eggdrop
53
sourcecode. You should always keep a tar.gz archive with the source of
54
your current Eggdrop on your shell. In the next step, you have to change
55
to your source directory (i.e.: /home/user/eggdrop1.6.0/) and type
56
the following command:</p>
59
<p>patch -p1 < ../path.to.the/patch</p>
62
<p>Once this is complete, execute the following command:</p>
65
<p>find . -name "*.rej" -print</p>
68
<p>If it returns a list with filenames ending with .rej extension, then
69
the patch didn't apply properly. Ensure that the patch is intended for
70
your version and that you have the original source. You should also try
71
to re-download the patch to ensure that the patch is not corrupted.</p>
73
<p>If the patch applied properly, the only thing left to do is to recompile
74
your Eggdrop and install the new modules and binaries.</p>
76
<p><a name="sect3"></a><strong>Creating and submitting a patch</strong></p>
78
<p>If you fixed a bug and/or changed something in Eggdrop's source
79
code, it would be really nice to let the dev team know about it, so they
80
can possibly apply it to next release of Eggdrop.</p>
82
<p>There are several steps to submit a patch to the eggdev team:</p>
87
<p>Create a directory with original source tree and one with
88
modified source tree.</p>
92
<p>Run the following:</p>
95
<p>diff -bur <original source directory> <modified
96
source directory> > patchname.patch</p>
99
<p>If your changes created any new files, use 'diff -burN'
105
<a href="mailto:patches@eggheads.org">patches@eggheads.org</a> with
106
the patch attached. The body should contain a detailed description
107
of what you changed and why you changed it. Don't forget to
108
include the Eggdrop version for which your patch was made. Also,
109
please send a second email with same info to
110
<a href="mailto:eggdev@eggheads.org">eggdev@eggheads.org</a>, this
111
time without the patch attached.</p>
116
<p><a name="sect4"></a><strong>Downloading a patch</strong></p>
119
<p>Many patches for eggdrop1.6.x can be found at the following
123
<p><a href="ftp://ftp.eggheads.org/pub/eggdrop/patches/1.6/">
124
ftp://ftp.eggheads.org/pub/eggdrop/patches/1.6/</a></p>
128
<p><em>Copyright © 1997 Robey Pointer<br>
129
Copyright © 1999, 2000, 2001, 2002, 2003, 2004
130
<a href="http://www.eggheads.org/"> Eggheads Development Team</a></em></p>
added
removed
doc/html/patch-howto.html
