2
Last revised: December 07, 2003
3
_________________________________________________________________
8
The purpose of this document is to show you what a patch is and how you
9
can create, apply, download, and submit a patch.
14
3. Creating and submitting a patch
15
4. Downloading a patch
20
The following are some common terms used in this document:
23
A patch is an update to the source code of a program (here Eggdrop).
24
Be careful, every patch is designed for a special Eggdrop version
25
and cannot be applied on every bot!
30
To apply a patch to an Eggdrop, you have to first obtain the Eggdrop
31
source code. You should always keep a tar.gz archive with the source of
32
your current Eggdrop on your shell. In the next step, you have to change
33
to your source directory (i.e.: /home/user/eggdrop1.6.16/) and type
34
the following command:
36
patch -p1 < ../path.to.the/patch
38
Once this is complete, execute the following command:
40
find . -name "*.rej" -print
42
If it returns a list with filenames ending with .rej extension, then the
43
patch didn't apply properly. Ensure that the patch is intended for your
44
version and that you have the original source. You should also try to
45
re-download the patch to ensure that the patch is not corrupted.
47
If the patch applied properly, the only thing left to do is to recompile
48
your Eggdrop and install the new modules and binaries.
51
3. Creating and submitting a patch
53
If you fixed a bug and/or changed something in Eggdrop's source code, it
54
would be really nice to let the dev team know about it, so they can
55
possibly apply it to next release of Eggdrop.
57
There are several steps to submit a patch to the eggdev team:
59
1. Create a directory with original source tree and one with modified
64
diff -urN eggdrop1.6.original eggdrop1.6.modified > patchname.patch
66
DO NOT add any other diff options.
68
3. Send an e-mail to patches@eggheads.org with the patch attached. The
69
body should contain a detailed description of what you changed and
70
why you changed it. Don't forget to include the Eggdrop version for
71
which your patch was created.
73
You should also include the nick/handle/name you would like to be used
74
in the UPDATES1.6 file (if applicable).
76
Never modify src/patch.h or one of the UPDATES files. We will do it. If
77
your patch includes changes related to autotools (./configure, etc), do
78
NOT run autoconf, autoheader, etc; we will do this as well.
80
Also, please don't add credit lines all over the source when patching.
81
Patch contributors will receive credit in UPDATES1.6 and ChangeLog.
84
4. Downloading a patch
86
Many patches for eggdrop1.6.x can be found at the following location:
88
ftp://ftp.eggheads.org/pub/eggdrop/patches/1.6
89
_________________________________________________________________
91
Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004 Eggheads Development Team
added
removed
doc/PATCH-HOWTO
