From bf14a2fa1b06b96427b5aeafe8a08c892806038c Mon Sep 17 00:00:00 2001 From: fred Date: Sun, 24 Mar 2002 20:10:00 +0000 Subject: [PATCH] lilypond-0.1.58 --- Documentation/PATCHES.pod | 118 -------------------------------------- Documentation/Rules.make | 1 - init/Makefile | 8 --- 3 files changed, 127 deletions(-) diff --git a/Documentation/PATCHES.pod b/Documentation/PATCHES.pod index 6e5e1a134c..7fbc7480c0 100644 --- a/Documentation/PATCHES.pod +++ b/Documentation/PATCHES.pod @@ -44,7 +44,6 @@ In F, enter a summary of changes: Then, from the top of Lily's source tree, type - make distclean # if you don't use --srcdir configure make-patch which leaves your patch as F<./patch-0.1.48.jcn1>. @@ -114,120 +113,3 @@ Then, make a patch as shown above. Han-Wen Nienhuys Just keep on sending those patches! -=head1 NAME - -PATCHES - track and distribute your code changes - -=head1 DESCRIPTION - -This page documents how to distribute your changes to GNU LilyPond - -=head1 ABSTRACT - -Distributing a change normally goes like this: - -=over 5 - -=item * - -make your fix/add your code - -=item * - -generate a patch, - -=item * - -e-mail your patch to one of the mailing lists -gnu-music-discuss@gnu.org or bug-gnu-music@gnu.org -(or if you're a bit shy, to the maintainer). - -=back - -=head1 GENERATING A PATCH - -In F, set TOPLEVEL_MY_PATCH_LEVEL: - - VERSION: - ... - TOPLEVEL_MY_PATCH_LEVEL = jcn1 - -In F, enter a summary of changes: - - NEWS: - pl 0.1.48.jcn1 - - added PATCHES.pod - -Then, type something like - - make-dist - mv out/lilypond-0.1.48.jcn1.tar.gz ../releases - make-patch - -which leaves your patch as F<./patch-0.1.48.jcn1>. - -or even simpler: - - release - - tar-ball: ../patches/patch-0.1.48.jcn1.gz - patch: ../patches/patch-0.1.48.jcn1.gz - updeet: ../test/updeet - -=head1 PREREQUISITES - -For creating a patch you need - -=over 5 - -=item * - -All items mentioned in F. You're not going to send a patch -that you haven't even built, right? - -=item * - -GNU Diff - -=item * - -Python (version 1.4 or newer). -You can of course make a patch by hand, which would go something like: - - make distclean - cd .. - diff -urN lilypond-0.1.48 lilypond-0.1.48.jcn1 > patch-0.1.48.jcn1 - -but there are handy python scripts available. If you're doing development, -you'll need Python for other LilyPond scripts anyway. - -=item * - -The Lily directory structure, which looks like: - - lilypond-0.1.48/ - patches/ - releases/ - test/ - -=back - -=head1 SYNCHRONISE - -If you're not very quick with sending your patch, there's a good chance -that an new release of LilyPond comes available. In such a case (and -sometimes for other unkown reasons :-), the maintainer will probably ask -you to make a new patch against the latest release. -Your best bet is to download the latest release, and apply your patch -against this new source tree: - - cd lilypond-0.1.49 - zpatch -p0 -E < ../patches/patch-0.1.48.jcn1.gz - -Then, make a patch as shown above. - -=head1 MAINTAINER - -Han-Wen Nienhuys - -Just keep on sending those patches! diff --git a/Documentation/Rules.make b/Documentation/Rules.make index fd0b391a2e..b8e14d7d8c 100644 --- a/Documentation/Rules.make +++ b/Documentation/Rules.make @@ -39,7 +39,6 @@ do_pod2html=$(POD2HTML5003) $(outdir)/%.html: %.pod $(depth)/VERSION $(do_pod2html) -# $(outdir)/%.5: %.pod $(pod2groff) diff --git a/init/Makefile b/init/Makefile index 1422d5d2aa..1e846bdbbf 100644 --- a/init/Makefile +++ b/init/Makefile @@ -1,17 +1,11 @@ # init/Makefile - -# subdir level: -# depth = .. -# # generic stuff/Makefile # include ./$(depth)/make/Include.make -# list of distribution files: -# INIFILES = $(wildcard *.ly) DISTFILES = Makefile $(INIFILES) @@ -20,11 +14,9 @@ DISTFILES = Makefile $(INIFILES) FONT_FILES = $(wildcard $(depth)/mf/*[0-9].mf) TABLES = $(patsubst $(depth)/mf/%.mf,%.ly,$(FONT_FILES)) - localclean: rm -f $(TABLES) - INSTALLATION_DIR=$(datadir)/lilypond/ INSTALLATION_FILES=$(INIFILES) -- 2.39.5