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
19 o Add changes to NEWS, and add yourself to
20 Documentation/AUTHORS.pod
24 o e-mail your patch to one of the mailing lists gnu-
25 music-discuss@gnu.org or bug-gnu-music@gnu.org
28 In VERSION, set TOPLEVEL_MY_PATCH_LEVEL:
32 TOPLEVEL_MY_PATCH_LEVEL = jcn1
34 In NEWS, enter a summary of changes:
40 Then, from the top of Lily's source tree, type
44 which leaves your patch as ./patch-0.1.48.jcn1.
46 If you didn't configure Lily using --srcdir, you can do:
50 tar-ball: ../patches/patch-0.1.48.jcn1.gz
51 patch: ../patches/patch-0.1.48.jcn1.gz
52 updeet: ../test/updeet
56 For creating a patch you need
58 o All items mentioned in INSTALL. You're not going to
59 send a patch that you haven't even built, right?
64 12/May/98 LilyPond 0.1.63 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 following LilyPond development regularly, you
95 probably want to download just the patch for each
96 subsequent release. After downloading the patch (into the
97 patches directory, of course), simply apply it:
99 gzip -dc ../patches/patch-0.1.49.gz | patch -p1 -E
101 and don't forget to make automatically generated files:
108 If you're not very quick with sending your patch, there's
109 a good chance that an new release of LilyPond comes
110 available. In such a case (and sometimes for other unkown
111 reasons :-), the maintainer will probably ask you to make
112 a new patch against the latest release. Your best bet is
113 to download the latest release, and apply your patch
114 against this new source tree:
117 gzip -dc ../patches/patch-0.1.48.jcn1.gz | patch -p1 -E
121 Then, make a patch as shown above.
123 1) patches don't include automatically generated files,
125 and files generated by configure.
130 12/May/98 LilyPond 0.1.63 2
136 PATCHES(1) LilyPond documentation PATCHES(1)
140 Han-Wen Nienhuys <hanwen@cs.uu.nl>
142 Just keep on sending those patches!
196 12/May/98 LilyPond 0.1.63 3