-1.4.1.jcn4
+1.4.2.jcn1
==========
+* Included mktexnam.patch (again?).
+
+* Documentation fix (Mark Hindley).
+
+* Debian patch and bashism fix (Anthony).
+
+* Bugfix: local-install should depend on $(INSTALLATION_FILES). This fixes
+./configure; make install in buildscripts/ (Michael Vanier).
+
+* Removed les-nereides from short-examples, as it is tweaked a lot,
+contrary to what the webpage claims (didn't know that).
+
+1.4.2
+=====
+
* Glossary fixes (Thanks Jean-Pierre Coulon).
1.4.1.jcn3
@uref{ftp://ftp.xcf.berkeley.edu/pub/xdelta/, xdelta}.
This is much safer than using patches, and is the recommended way.
-The following command produces @file{lilypond-1.4.1.tar.gz} from
-@file{lilypond-1.4.0.tar.gz} identical (up to compression dates) to the .1
+The following command produces @file{lilypond-1.4.3.tar.gz} from
+@file{lilypond-1.4.2.tar.gz} identical (up to compression dates) to the .3
on the FTP site.
@example
- xdelta patch lilypond-1.4.0-1.4.1.xd lilypond-1.4.0.tar.gz
+ xdelta patch lilypond-1.4.2-1.4.3.xd lilypond-1.4.2.tar.gz
@end example
@end itemize
@command{apt-get} as root:
@example
- apt-get install lilypond
+ apt-get install lilypond lilypond-doc
@end example
@itemize @bullet
@item @uref{http://packages.debian.org/lilypond,http://packages.debian.org/lilypond}
@item @uref{http://people.debian.org/~foka/lilypond/,http://people.debian.org/~foka/lilypond/}
-for latest semi-unofficial build of LilyPond 1.3.121 for Debian 2.2 (potato) users.
+for latest semi-unofficial build of LilyPond 1.4.2 for Debian 2.2 (potato) users.
The official stable Debian 2.2 is stuck with the old LilyPond-1.3.24.
Since LilyPond-1.4 has been released, the older lilypond1.3 Debian
package is now obsolete.
$ su - root
# dpkg --purge lilypond lilypond1.3
# exit
- $ tar xzf lilypond-1.4.1.tar.gz
- $ cd lilypond-1.4.1
- $ dch -p -v 1.4.1-0.local.1 "Local build."
- $ debuild
+ $ tar xzf lilypond-1.4.3.tar.gz
+ $ cd lilypond-1.4.3
+ $ dch -p -v 1.4.3-0.local.1 "Local build."
+ $ debuild -B
$ su - root
- # dpkg -i ../lilypond_1.4.1*.deb
+ # dpkg -i ../lilypond_1.4.3*.deb
# exit
$
@end example
+Use command @command{debuild} instead of @command{debuild -B} if you have
+a very fast machine and want to build the HTML, PS and DVI documentation
+too.
+
For compilation on a Debian GNU/Linux system you need these packages,
in addition to the those needed for running:
@node pmx2ly
@section pmx2ly
-PMX is a Musixtex preprocessor written by Don Simons, see
+PMX is a MusiXTeX preprocessor written by Don Simons, see
@uref{http://icking-music-archive.sunsite.dk/Misc/Music/musixtex/software/pmx/}.
Report bugs to @email{bug-gnu-music@@gnu.org}.
The value of @code{autoBeamSettings} is changed using
@code{\override} and unset using @code{\revert}:
@example
-\property Voice.autoBeamSettings \override #'(@var{BE} @var{N} @var{M} @var{P} @var{Q}) = @var{dur}
-\property Voice.autoBeamSettings \revert #'(@var{BE} @var{N} @var{M} @var{P} @var{Q})
+\property Voice.autoBeamSettings \override #'(@var{BE} @var{P} @var{Q} @var{N} @var{M}) = @var{dur}
+\property Voice.autoBeamSettings \revert #'(@var{BE} @var{P} @var{Q} @var{N} @var{M})
@end example
Here, @var{BE} is the symbol @code{begin} or @code{end}. It determines
whether the rule applies to begin or end-points. The quantity
-@var{N}/@var{M} refers to a time signature (wildcards, `@code{* *}' may
-be entered to designate all time signatures), @var{P}/@var{Q} refers to
-the length of the beamed notes (and `@code{* *}' designates notes of any
-length).
+@var{P}/@var{Q} refers to the length of the beamed notes (and `@code{*
+*}' designates notes of any length), @var{N}/@var{M} refers to a time
+signature (wildcards, `@code{* *}' may be entered to designate all time
+signatures).
For example, if you want automatic beams to end on every quarter note,
you can use the following:
You can also restrict rules to specific time signatures. A rule that
should only be applied in @var{N}/@var{M} time signature is formed by
-replacing the first asterisks by @var{N} and @var{M}. For example, a
+replacing the second asterisks by @var{N} and @var{M}. For example, a
rule for 6/8 time exclusively looks like
@example
\property Voice.autoBeamSettings \override
- #'(begin 6 8 * *) = ...
+ #'(begin * * 6 8) = ...
@end example
If you want a rule to apply to certain types of beams, you can use the
-second pair of asterisks. Beams are classified according to the shortest
+first pair of asterisks. Beams are classified according to the shortest
note they contain. For a beam ending rule that only applies to beams
-with 32nd notes (and no shorter notes), you would use @code{(end * * 1
-32)}.
+with 32nd notes (and no shorter notes), you would use @code{(end 1
+32 * *)}.
@c not true
@c Automatic beams can not be put on the last note in a score.
These binaries are cross compiled for Windows on a GNU/Linux box. You
may want to check out the
-@uref{http://www.lilypond.org/gnu-windows/cross-1.1.8.tar.gz,cross
-compilation scripts}.
+@uref{http://www.lilypond.org/gnu-windows/cross.tar.gz,cross compilation
+scripts}.
@section Windows installation specifics
@item @var{guile-1.4-gnu-windows.patch}
You may (Cygwin gets better every day) need this patch to compile GUILE.
@item @var{cygwin-installer.patch}
-Apply this patch to the @file{cinstall} directory of Cygwin, to get the
-LilyPond installer.
+Apply this patch to the @file{cinstall} directory of
+@file{winsup-src/cinstall}, to get the LilyPond installer.
+
+Compiling @file{setup.exe} has been complicated a bit with the
+introduction of the non-feature bzip2. Here's how I did it:
+@quotation
+@example
+ tar xjf cygwin-src-20010531.tar.bz2
+ tar xjf winsup-src-20010531.tar.bz2
+ tar xzf mingw-20010424-1.tar.gz
+ cd winsup/cinstall
+ patch < ../../cygwin-installer.patch
+ cp /home/cygwin/cygwin-1.3.2/usr/lib/mingw/crt2.o .
+ cd ../bzip
+ MINGW32=yes CFLAGS='-mno-cygwin' ./configure
+ make
+ cd -
+ make w32api_lib=/home/cygwin/cygwin-1.3.2/usr/lib/w32api \
+ CXX='g++ -L/home/cygwin/cygwin-1.3.2/usr/lib/mingw'
+@end example
+@end quotation
@item @var{--prefix=/usr/lilypond-x.y.x}
The standard binary installation installs LilyPond into its own prefix.
We think it's silly, but do this is on special request of Windows users.
If you're lucky, after running @file{setup.exe} you're all set up.
Open a LilyPond shell (or any bash shell), and type
+
+@quotation
@example
lilypond --help
@end example
+@end quotation
If you don't see something similar to
+
+@quotation
@example
Usage: lilypond [OPTION]... [FILE]...
-h,--help this help
[..]
@end example
+@end quotation
you should try adding @file{/usr/lilypond-x.y.z/bin} to your @var{PATH},
do:
+
+@quotation
@example
PATH=/usr/lilypond-1.3.147/bin:$PATH
@end example
+@end quotation
and try again.
README_FILES = DEDICATION COPYING NEWS CHANGES ROADMAP
README_TXT_FILES = AUTHORS.txt README.txt INSTALL.txt FAQ.txt
IN_FILES := $(wildcard *.in)
-EXTRA_DIST_FILES = lilypond-font-lock.el lilypond-mode.el lilypond-init.el vimrc VERSION $(README_FILES) $(SCRIPTS) $(IN_FILES) emacsclient.patch
+EXTRA_DIST_FILES = lilypond-font-lock.el lilypond-mode.el lilypond-init.el vimrc VERSION $(README_FILES) $(SCRIPTS) $(IN_FILES) emacsclient.patch mktexnam.patch
NON_ESSENTIAL_DIST_FILES = $(README_TXT_FILES)
INSTALLATION_DIR=$(datadir)
INSTALLATION_FILES=$(configuration) VERSION
-not -name '*.vr' -not -name '*.yp' -not -name '*.ky' \
-not -name '*.pg' -not -name '*.tmp' -not -name '*.toc' \
-not -name '*.fns' -not -name '*.cps' -not -name '*.nexi' \
- -not -name '*.texi' -not -name '*.texidoc' \
+ -not -name '*.texi' -not -name '*.texidoc' -not -name '*.tp' \
-not -name '*.log' -not -name 'out-www' -not -name '*.dep' \
> $(outdir)/weblist
ls *.png *.html >> $(outdir)/weblist
MAJOR_VERSION=1
MINOR_VERSION=4
PATCH_LEVEL=2
-MY_PATCH_LEVEL=
+MY_PATCH_LEVEL=jcn1
# use the above to send patches: MY_PATCH_LEVEL is always empty for a
# released version.
-# bin/Makefile
-
depth = ..
-STEPMAKE_TEMPLATES=script install install-out po
-include $(depth)/make/stepmake.make
+#STEPMAKE_TEMPLATES=script install install-out po
+STEPMAKE_TEMPLATES=script install po
INSTALLATION_FILES=$(outdir)/gettext.py
INSTALLATION_DIR=$(datadir)/python
+include $(depth)/make/stepmake.make
+
# Should we install these? This should be handled by sysadmin or
# packager but if she forgets...
#INSTALLATION_OUT_SUFFIXES=1
all: $(outdir)/gettext.py
-
-
-
-
-
-#!@BASH@
+#!@SHELL@
name=install-info-html
version=1.0
#
# print usage
#
-function help ()
+help ()
{
cat << EOF
$name $version
}
-function cleanup ()
+cleanup ()
{
$debug_echo "cleaning ($?)..."
}
EXTRA_DIST_FILES = README.Debian $(CONF_FILES) \
control.foka control.potato \
lilypond.dirs lilypond.doc-base lilypond.links \
- lilypond-doc.dirs lilypond-doc.doc-base lilypond-doc.README.Debian
+ lilypond-doc.dirs lilypond-doc.doc-base lilypond-doc.README.Debian \
+ lilypond1.3.copyright
#OUTCONF_FILES = $(addprefix $(outdir)/, $(basename $(CONF_FILES))) $(OUTIN_FILES)
OUTCONF_FILES = $(OUTIN_FILES)
OUT_DIST_FILES = $(OUTIN_FILES)
+lilypond (1.4.2-1) unstable; urgency=low
+
+ * New upstream release.
+ * Moved "bibtex2html, gs | gs-aladdin, netpbm (>= 2:9.10-1)"
+ from Build-Depends to Build-Depends-Indep because these packages
+ are only needed for building lilypond-doc.
+
+ -- Anthony Fok <foka@debian.org> Tue, 29 May 2001 02:26:58 -0600
+
lilypond (1.4.1-1) unstable; urgency=low
* New upstream release. (Closes: Bug#97598)
Source: lilypond
-Build-Depends: debhelper (>= 3.0.5), python-base (>= 1.5.2-4), libguile-dev (>= 1:1.4-9), tetex-bin, libkpathsea-dev, tetex-extra, flex, bison, texinfo (>= 4.0-1), bibtex2html, groff, gs | gs-aladdin, netpbm (>= 2:9.10-1), m4, gettext (>= 0.10.36-1)
+Build-Depends: debhelper (>= 3.0.5), python-base (>= 1.5.2-4), libguile-dev (>= 1:1.4-9), tetex-bin, libkpathsea-dev, tetex-extra, flex, bison, texinfo (>= 4.0-1), groff, m4, gettext (>= 0.10.36-1)
+Build-Depends-Indep: bibtex2html, gs | gs-aladdin, netpbm (>= 2:9.10-1)
Section: tex
Priority: optional
Maintainer: Anthony Fok <foka@debian.org>
Package: lilypond-doc
Section: doc
Architecture: all
-Recommends: lilypond (= ${Source-Version})
+Suggests: lilypond (>= 1.4.1-1)
Suggests: postscript-viewer, www-browser
Description: LilyPond Documentation in HTML, PS and DVI formats
This package contains the HTML, PostScript and DVI documentation for the
Source: lilypond
-Build-Depends: debhelper (>= 3.0.5), python-base (>= 1.5.2-4), libguile-dev (>= 1:1.4-9), tetex-bin, libkpathsea-dev, tetex-extra, flex, bison, texinfo (>= 4.0-1), bibtex2html, groff, gs | gs-aladdin, netpbm (>= 2:9.10-1), m4, gettext (>= 0.10.36-1)
+Build-Depends: debhelper (>= 3.0.5), python-base (>= 1.5.2-4), libguile-dev (>= 1:1.4-9), tetex-bin, libkpathsea-dev, tetex-extra, flex, bison, texinfo (>= 4.0-1), groff, m4, gettext (>= 0.10.36-1)
+Build-Depends-Indep: bibtex2html, gs | gs-aladdin, netpbm (>= 2:9.10-1)
Section: tex
Priority: optional
Maintainer: Anthony Fok <foka@debian.org>
Package: lilypond-doc
Section: doc
Architecture: all
-Recommends: lilypond (= ${Source-Version})
+Suggests: lilypond (>= 1.4.1-1)
Suggests: postscript-viewer, www-browser
Description: LilyPond Documentation in HTML and PS formats
This package contains the HTML and PostScript documentation for the
-Source: lilypond1.3
-Build-Depends: debhelper (>= 2.0.72), python-base (>= 1.5.2-4), libguile6-dev, tetex-bin, tetex-dev, tetex-extra, flex, bison, texinfo (>= 4.0-1), groff, gs, netpbm, pnmtopng, m4, gettext (>= 0.10.35-13)
+Source: lilypond
+Build-Depends: debhelper (>= 2.0.72), python-base (>= 1.5.2-4), libguile6-dev, tetex-bin, tetex-lib, tetex-extra, flex, bison, texinfo (>= 4.0-4), groff, m4, gettext (>= 0.10.35-13)
+Build-Depends-Indep: gs | gs-aladdin, netpbm, pnmtopng
Section: tex
Priority: optional
Maintainer: Anthony Fok <foka@debian.org>
-Standards-Version: 3.2.1
+Standards-Version: 3.1.1
-Package: lilypond1.3
+Package: lilypond
Architecture: any
-Replaces: lilypond
-Provides: lilypond
+Replaces: lilypond1.3
+Provides: lilypond1.3
Depends: ${shlibs:Depends}, tetex-bin (>= 1.0.5-1), python-base (>= 1.5.2-4), guile
-Recommends: tetex-extra (>= 1.0-1)
-Conflicts: lilypond, musixtex-fonts
+Recommends: lilypond-doc, tetex-extra (>= 1.0-1)
+Conflicts: lilypond, lilypond1.3 (<= 1.3.132-1), musixtex-fonts
Description: A program for printing sheet music.
LilyPond is a music typesetter. It produces beautiful sheet music
using a high level description file as input. LilyPond is part of
the GNU Project.
- .
- This is the developmental 1.3 branch of LilyPond. It is not intended for
- use with stable projects, although 1.3.x is most likely to be less buggy
- and much more featureful than then the old "stable" 1.2.17.
.
URLs: http://www.cs.uu.nl/~hanwen/lilypond/
http://www.xs4all.nl/~jantien/lilypond/
http://www.lilypond.org/
Authors: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Jan Nieuwenhuizen <janneke@gnu.org>
+
+Package: lilypond-doc
+Section: doc
+Architecture: all
+Suggests: lilypond (>= 1.4.1-1)
+Suggests: postscript-viewer, www-browser
+Description: LilyPond Documentation in HTML, PS and DVI formats
+ This package contains the HTML, PostScript and DVI documentation for the
+ LilyPond music typestting software.
+
+Package: lilypond1.3
+Architecture: all
+Depends: lilypond (>= 1.3.150-1)
+Description: Dummy package for transition to new stable lilypond.
+ This dummy package provides a transition from the previous lilypond1.3
+ package back to a newer lilypond because the stable 1.4 series has arrived.
+ .
+ Please feel free to remove this dummy package after you have upgraded
+ to the latest lilypond.
--- /dev/null
+This is a dummy package to aid the transition from the old
+"lilypond1.3" package to the newer "lilypond" package.
+It was created by Anthony Fok <foka@debian.org>
+Mon, 16 Apr 2001 22:17:10 -0600
+
+Copyright:
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License with
+ the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
+ if not, write to the Free Software Foundation, Inc., 59 Temple Place,
+ Suite 330, Boston, MA 02111-1307 USA
r_doc = debian/$(package)-doc
d = usr/share/doc/$(package)
-# TELY_FILES := $(notdir $(wildcard Documentation/user/*.tely))
-# DVI_FILES = $(addprefix Documentation/user/out/, $(TELY_FILES:.tely=.dvi))
-# PS_FILES = $(DVI_FILES:.dvi=.ps)
-
# "main_memory = 263000" in /etc/texmf/texmf.cnf isn't large enough
# for latex to process standchen.dvi.latex, so adding extra_mem_* ...
-export extra_mem_top=100000
-export extra_mem_bot=100000
-export MODE=ljfour
-export BDPI=600
-export MAILADDRESS=lilypond@packages.debian.org
+export extra_mem_top = 100000
+export extra_mem_bot = 100000
+export MODE = ljfour
+export BDPI = 600
+export USER_CFLAGS = -DDEBIAN
+export DEB_BUILD = yes
+export MAILADDRESS = lilypond@packages.debian.org
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
--prefix=/usr --enable-optimise \
--infodir='$${prefix}/share/info' \
--mandir='$${prefix}/share/man'
- $(MAKE) USER_CFLAGS=-DDEBIAN all
+ $(MAKE)
touch build-stamp
# Add here commands to install the package into debian/tmp.
dh_installdirs
- $(MAKE) prefix=$(PWD)/$(r)/usr USER_CFLAGS=-DDEBIAN install
+ $(MAKE) prefix=$(PWD)/$(r)/usr install
# Change from an absolute symlink to a relative symlink (Lintian)
if [ -L $(r)/usr/share/lilypond/cmtfm ]; then \
dh_installdocs
dh_installchangelogs
dh_link
- dh_compress
+ dh_compress -Xusr/share/doc/lilypond/html/
dh_fixperms
dh_installdeb
dh_gencontrol
dh_compress
dh_fixperms
dh_installdeb
-# dh_shlibdeps
- # Ugh, ugly kludge to avoid the circular symlinks under html/
- cd debian/lilypond && dpkg-shlibdeps -T../substvars -dDepends \
- usr/bin/lilypond usr/bin/midi2ly
+ dh_shlibdeps
dh_gencontrol
# dh_makeshlibs
dh_md5sums
-# input/Makefile
-
depth = ..
SUBDIRS=bugs test regression tutorial no-notation ascii-art
-examples=trip star-spangled-banner paddy twinkle nereides
+# nereides is tweaked a lot, can't do (read webpage)
+examples=trip star-spangled-banner paddy twinkle #nereides
LOCALSTEPMAKE_TEMPLATES=ly mutopia
EXTRA_DIST_FILES=paddy.abc
export MFINPUTS:=$(topdir)/mf/:$(MFINPUTS)::
export TEXINPUTS:=$(topdir)/mf/out/:$(topdir)/tex/:$(topdir)/ps/:$(TEXINPUTS):$(pwd)::
export LILYINCLUDE:=$(topdir)/ps:$(topdir)/scm:$(topdir)/ly:$(topdir)/mf/out::$(TEX_TFMDIR):$(LILYINCLUDE)
-export TFMFONTS=$(topdir)/mf/out:
+export TFMFONTS:=$(topdir)/mf/out:
+
+ifdef DEB_BUILD
+export PKFONTS := $(topdir)/mf/out
+export MT_DESTROOT := $(topdir)/mf/out
+export DVIPSMAKEPK := mktexpk --destdir $(topdir)/mf/out
+endif
export LILYPONDPREFIX:=$(depth)/
export PYTHONPATH:=$(buildscript-dir)/$(outdir):$(PYTHONPATH)
--- /dev/null
+--- mktexnam.orig Sun Mar 4 19:29:45 2001
++++ mktexnam Tue May 8 20:28:57 2001
+@@ -158,6 +158,7 @@
+ MT_PKDESTDIR=$DEST
+ MT_TFMDESTDIR=$DEST
+ MT_MFDESTDIR=$DEST
++ MT_DESTROOT=foobar
+ MT_NAMEPART=;;
+ *) # Relative destdir => append to the default.
+ MT_NAMEPART=$DEST;;
--- /dev/null
+ depth = ../../..
+ include $(depth)/ports/ports.make
+
--- /dev/null
+ depth = ../../..
+ include $(depth)/ports/ports.make
+
--- /dev/null
+ depth = ../../..
+ include $(depth)/ports/ports.make
+
--- /dev/null
+ depth = ../../..
+ include $(depth)/ports/ports.make
+
--- /dev/null
+ depth = ../../..
+ include $(depth)/ports/ports.make
+
'''Report the error S. Exit by raising an exception. Please
- do not abuse by trying to catch this error. If you donn't want
+ do not abuse by trying to catch this error. If you do not want
a stack trace, write to the output directly.
RETURN VALUE
local-install-outfiles:
# urg, parameterise
-local-install-files:
+local-install-files: $(INSTALLATION_FILES)
$(PRE_INSTALL)
-$(INSTALL) -d $(INSTALLATION_DIR)
$(foreach i, $(INSTALLATION_FILES),\