4 PATCHES(1) LilyPond documentation PATCHES(1)
8 PATCHES - track and distribute your code changes
11 This page documents how to distribute your changes to GNU
15 Distributing a change normally goes like this:
17 o make your fix/add your code
21 o e-mail your patch to one of the mailing lists gnu-
22 music-discuss@gnu.org or bug-gnu-music@gnu.org (or if
23 you're a bit shy, to the maintainer).
26 In VERSION, set TOPLEVEL_MY_PATCH_LEVEL:
30 TOPLEVEL_MY_PATCH_LEVEL = jcn1
32 In NEWS, enter a summary of changes:
38 Then, from the top of Lily's source tree, type
40 make distclean # if you don't use --srcdir configure
43 which leaves your patch as ./patch-0.1.48.jcn1.
45 If you didn't configure Lily using --srcdir, you can do:
49 tar-ball: ../patches/patch-0.1.48.jcn1.gz
50 patch: ../patches/patch-0.1.48.jcn1.gz
51 updeet: ../test/updeet
55 For creating a patch you need
57 o All items mentioned in INSTALL. You're not going to
58 send a patch that you haven't even built, right?
64 2/Apr/98 LilyPond 0.1.57 1
70 PATCHES(1) LilyPond documentation PATCHES(1)
75 o Python (version 1.4 or newer). You can of course
76 make a patch by hand, which would go something like:
80 diff -urN lilypond-0.1.48 lilypond-0.1.48.jcn1 > patch-0.1.48.jcn1
82 but there are handy python scripts available. If
83 you're doing development, you'll need Python for
84 other LilyPond scripts anyway.
86 o The Lily directory structure, which looks like:
94 If you're not very quick with sending your patch, there's
95 a good chance that an new release of LilyPond comes
96 available. In such a case (and sometimes for other unkown
97 reasons :-), the maintainer will probably ask you to make
98 a new patch against the latest release. Your best bet is
99 to download the latest release, and apply your patch
100 against this new source tree:
103 zpatch -p0 -E < ../patches/patch-0.1.48.jcn1.gz
105 Then, make a patch as shown above.
108 Han-Wen Nienhuys <hanwen@cs.ruu.nl>
110 Just keep on sending those patches! =head1 NAME
112 PATCHES - track and distribute your code changes
115 This page documents how to distribute your changes to GNU
119 Distributing a change normally goes like this:
121 o make your fix/add your code
125 o e-mail your patch to one of the mailing lists gnu-
126 music-discuss@gnu.org or bug-gnu-music@gnu.org (or if
130 2/Apr/98 LilyPond 0.1.57 2
136 PATCHES(1) LilyPond documentation PATCHES(1)
139 you're a bit shy, to the maintainer).
142 In VERSION, set TOPLEVEL_MY_PATCH_LEVEL:
146 TOPLEVEL_MY_PATCH_LEVEL = jcn1
148 In NEWS, enter a summary of changes:
154 Then, type something like
157 mv out/lilypond-0.1.48.jcn1.tar.gz ../releases
160 which leaves your patch as ./patch-0.1.48.jcn1.
166 tar-ball: ../patches/patch-0.1.48.jcn1.gz
167 patch: ../patches/patch-0.1.48.jcn1.gz
168 updeet: ../test/updeet
172 For creating a patch you need
174 o All items mentioned in INSTALL. You're not going to
175 send a patch that you haven't even built, right?
179 o Python (version 1.4 or newer). You can of course
180 make a patch by hand, which would go something like:
184 diff -urN lilypond-0.1.48 lilypond-0.1.48.jcn1 > patch-0.1.48.jcn1
186 but there are handy python scripts available. If
187 you're doing development, you'll need Python for
188 other LilyPond scripts anyway.
190 o The Lily directory structure, which looks like:
196 2/Apr/98 LilyPond 0.1.57 3
202 PATCHES(1) LilyPond documentation PATCHES(1)
211 If you're not very quick with sending your patch, there's
212 a good chance that an new release of LilyPond comes
213 available. In such a case (and sometimes for other unkown
214 reasons :-), the maintainer will probably ask you to make
215 a new patch against the latest release. Your best bet is
216 to download the latest release, and apply your patch
217 against this new source tree:
220 zpatch -p0 -E < ../patches/patch-0.1.48.jcn1.gz
222 Then, make a patch as shown above.
225 Han-Wen Nienhuys <hanwen@cs.ruu.nl>
227 Just keep on sending those patches!
262 2/Apr/98 LilyPond 0.1.57 4