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
42 which leaves your patch as ./patch-0.1.48.jcn1.
44 If you didn't configure Lily using --srcdir, you can do:
48 tar-ball: ../patches/patch-0.1.48.jcn1.gz
49 patch: ../patches/patch-0.1.48.jcn1.gz
50 updeet: ../test/updeet
54 For creating a patch you need
56 o All items mentioned in INSTALL. You're not going to
57 send a patch that you haven't even built, right?
64 28/Apr/98 LilyPond 0.1.60 1
70 PATCHES(1) LilyPond documentation PATCHES(1)
73 o Python (version 1.4 or newer). You can of course
74 make a patch by hand, which would go something like:
78 diff -urN lilypond-0.1.48 lilypond-0.1.48.jcn1 > patch-0.1.48.jcn1
80 but there are handy python scripts available. If
81 you're doing development, you'll need Python for
82 other LilyPond scripts anyway.
84 o The Lily directory structure, which looks like:
92 If you're following LilyPond development regularly, you
93 probably want to download just the patch for each
94 subsequent release. After downloading the patch (into the
95 patches directory, of course), simply apply it:
97 gzip -dc ../patches/patch-0.1.49.gz | patch -p1 -E
99 and don't forget to make automatically generated files:
106 If you're not very quick with sending your patch, there's
107 a good chance that an new release of LilyPond comes
108 available. In such a case (and sometimes for other unkown
109 reasons :-), the maintainer will probably ask you to make
110 a new patch against the latest release. Your best bet is
111 to download the latest release, and apply your patch
112 against this new source tree:
115 gzip -dc ../patches/patch-0.1.48.jcn1.gz | patch -p1 -E
119 Then, make a patch as shown above.
121 1) patches don't include automatically generated files,
123 and files generated by configure.
126 Han-Wen Nienhuys <hanwen@cs.ruu.nl>
130 28/Apr/98 LilyPond 0.1.60 2
136 PATCHES(1) LilyPond documentation PATCHES(1)
139 Just keep on sending those patches!
196 28/Apr/98 LilyPond 0.1.60 3