+++ /dev/null
-\input texinfo @c -*-texinfo-*-
-@setfilename internals.info
-@settitle LilyPond internals
-
-
-@node Top, , (dir), (dir)
-@top
-
-
+++ /dev/null
-@node More information
-@section Resources
-
+++ /dev/null
-@c -*-texinfo-*-
-
-@node Utility programs
-@chapter Utility programs
-
-@menu
-@end menu
-
-
-
+++ /dev/null
-@c -*-texinfo-*-
-
-@c TODO: LilyPond Lilypond lilypond
-
-@node Toet
-@chapter Toet
-
-The music is described in a text file, using a simple music language.
-LilyPond reads that text file and generates music that you can print or
-view.
-
-Therefore, creating music notation with LilyPond is done in two steps.
-Using a text editor, you write down the notes to print. Then, you run
-LilyPond to get your printed output.
-
-
-This tutorial starts with a small introduction to the LilyPond music
-language. After this first contact, we will show you how to produce
-printed output; you should then be able to create your first sheets of
-music.
-
-The tutorial continues with a bit more elaborate example of real music.
-This piece introduces and explains some finer details of LilyPond.
-Then, a number of more complex examples follow, that will help you to
-produce most complex music with LilyPond.
-
-
-@menu
-* Music language of LilyPond:: First contact
-* Running LilyPond toet::
-@end menu
-
-
-
-@node Music language of LilyPond
-@section Music language of LilyPond
-
-This section shows how easy making music with LilyPond actually is. If
-you have not used LilyPond before, this section is for you.
-
-
-You get a simple note by typing its name, from @code{a} through @code{g}:
-
-@lilypond[verbatim, relative 1]
-a b c d e f g
-@end lilypond
-
-@separate
-
-A are sharp is made by adding @code{is}, a flat by adding @code{es}:
-
-@lilypond[verbatim, relative 0]
-fis aes cisis beses
-@end lilypond
-
-@separate
-
-The length of a note is specified by adding a number, @code{1} for a
-whole note, @code{2} for a halve note:
-
-@lilypond[verbatim, relative 1]
-a1 a2 a8 a4 a16 a8. a16
-@end lilypond
-
-@separate
-
-Adding a high quote @code{'}, raises the pitch by one octave, adding a
-``low quote'' @code{,} (a comma), lowers the pitch one octave:
-
-@lilypond[verbatim, relative 1]
-c c' c,,
-@end lilypond
-
-@separate
-
-If you type no octaviation quotes, LilyPond chooses the note that is
-closest to the previous one, which is often just the one you need. For
-example, @code{c f} goes up, and @code{c g} goes down:
-
-@lilypond[verbatim, relative 1]
-c f c g c
-@end lilypond
-
-@separate
-
-You can make a large interval by adding octaviation quotes. For example,
-@code{c f,} goes down, and @code{c g'} goes up:
-
-@lilypond[verbatim, relative 1]
-c f, f c' c g' c,
-@end lilypond
-
-@separate
-
-To get a rest you use note name @code{r}, to skip a note use note name
-@code{s}:
-
-@lilypond[verbatim, relative 1]
-r2 s4 r4
-@end lilypond
-
-@separate
-
-The meter can be specified using @code{\time}:
-
-@c \time -> \meter ?
-@lilypond[verbatim, relative 1]
-\time 3/4 c c c | R1 * 3/4
-@end lilypond
-
-@separate
-
-The key is specified using @code{\key}:
-
-@lilypond[verbatim, relative 0]
-\key f \major es as bes
-@end lilypond
-
-@separate
-
-Slurs are printed using parenthesis @code{()}, for phrasing slurs use
-@code{\(} and @code{\)}. You get a tie using @code{~}:
-
-@lilypond[verbatim, relative 1]
-c\( ( ) d ~ d \) c
-@end lilypond
-
-@separate
-
-A chord is made using angle brackets @code{<} and @code{>}:
-
-@lilypond[verbatim, relative 1]
-\oneVoice <a c> <b d> <c e>
-@end lilypond
-
-@separate
-
-suddenly lilypond bit really difficult:
-[explain about score -> \score and \notes]
-
-long chords; simultaneous music
-@lilypond[verbatim]
-\paper { linewidth = -1.0 }
-\score {
- \context Staff \notes \relative c'' <
- { \voiceOne a b c }
- { \voiceTwo c d e }
- >
-}
-@end lilypond
-
-@separate
-
-@lilypond[verbatim]
-\paper { linewidth = -1.0 }
-\score {
- \context GrandStaff \notes \relative c' <
- \context Staff=one { a' b c }
- \context Staff=two { \clef bass c,, d e }
- >
-}
-@end lilypond
-
-
-@node Running LilyPond toet
-@section Running LilyPond toet
-
-This section shows how to view and print music with LilyPond. If you
-want to test your setup of LilyPond, or try to run an example file
-yourself, then read this section.
-
-The first step is to create an text file with some music. Using your
-favorite text-editor, create @file{test.ly} containing
-
-@ignore
-
-NOTE: if you're reading this, ie, the Texinfo source itself, test.ly
-should of course contain:
-
- \score{
- \notes { c'4 e' g' }
- }
-
-@end ignore
-
-@example
-\score @{
- \notes @{ c'4 e' g' @}
-@}
-@end example
-
-@unnumberedsubsec Running LilyPond on Unix
-@cindex Unix, Running lilypond on
-@cindex ly2dvi
-
-To run LilyPond, you invoke ly2dvi to compile your LilyPond source file:
-
-@quotation
-@example
-ly2dvi -P test.ly
-@end example
-@end quotation
-
-You will see the following on your screen:
-
-@quotation
-@example
-GNU LilyPond 1.4.0
-Now processing: `/home/fred/ly/test.ly'
-Parsing...
-Interpreting music...[1]
- @emph{ ... some more text ... }
-PS output to test.ps...
-DVI output to test.dvi...
-@end example
-@end quotation
-
-The results are a ``DeVice Independent'' file
-(@file{test.dvi}) and a PostScript file (@file{test.ps}).
-
-@cindex DVI file
-
-@cindex Viewing music
-@cindex xdvi
-@cindex .dvi
-
-To view the @code{test.dvi} output, run Xdvi:
-
-@quotation
-@example
-xdvi test.dvi
-@end example
-@end quotation
-
-@c FIXME: should we say anything on xdvi-gs interaction?
-
-You should see the following in your main Xdvi window:
-@lilypond
-\score {
- \notes { c'4 e' g' }
-}
-@end lilypond
-
-When you're satisfied with the result, you can print the
-PostScript file:
-
-@quotation
-@example
-lpr test.ps
-@end example
-@end quotation
-If this does not make your printer produce a page of music, you should
-look into installing and configuring ghostscript. Refer to
-GhostScript's website at @uref{http://www.ghostscript.com}.
-@cindex GhostScript
-@cindex @code{lpr}
-@cindex Printing output
-
-@cindex PostScript
-@cindex .ps
-
-
-@unnumberedsubsec Running LilyPond on Windows
-
-
-On windows, you open a LilyPond shell, and then you invoke ly2dvi
-compile your LilyPond source file, just like on Unix:
-
-@quotation
-@example
-ly2dvi -P test.ly
-@end example
-@end quotation
-You will see the following on your screen:
-
-@c FIXME: leave this out, just refer to unix section?
-@c FIXME: commands run in dos shell: we can't redirect output
-@quotation
-@example
-GNU LilyPond 1.3.150
-Now processing: `/home/tim/ly/test.ly'
-Parsing...
-Interpreting music...[1]
- @emph{ ... some more text ... }
-PS output to test.ps...
-DVI output to test.dvi...
-@end example
-@end quotation
-
-To view the @code{test.dvi} output, run Yap
-
-@quotation
-@example
-yap test
-@end example
-@end quotation
-You should see the following in your Yap window
-@lilypond
-\score {
- \notes { c'4 e' g' }
-}
-@end lilypond
-
-@c FIXME: talk about newer Yap versions, proper gs installation?
-When you're satisfied with the result, you can print from within Yap
-(File/Print). Note that Yap may not display embedded PostScript symbols
-such as beams and slurs. Don't worry, they'll be printed anyway.
-
-You can also print the PostScript file directly from the
-command line using GSview:
-
-@quotation
-@example
-gsview32 /s test.ps
-@end example
-@end quotation
-
-
-
+++ /dev/null
-\version "1.3.146"
-
+++ /dev/null
-%define info yes
-
-Name: lilypond
-Version: @TOPLEVEL_VERSION@
-Release: 1
-License: GPL
-Group: Applications/Publishing
-Source0: ftp.cs.uu.nl:/pub/GNU/LilyPond/development/lilypond-@TOPLEVEL_VERSION@.tar.gz
-Summary: Create and print music notation
-URL: http://www.cs.uu.nl/~hanwen/lilypond
-BuildRoot: /tmp/lilypond-install
-# add lots of Buildreq: flex, bison, tetex, tetex-devel, tetex-latex, texinfo
-# better prereqs: tetex-latex, python, (mpost?) etc.
-Prereq: tetex
-
-
-%description
-LilyPond lets you create music notation. It produces
-beautiful sheet music from a high-level description file.
-
-%package documentation
-Summary: Prebuilt website containing all LilyPond documentation.
-Group: Applications/Publishing
-# BuildArchitectures: noarch
-
-%description documentation
-
-The documentation of LilyPond, both in HTML and PostScript.
-
-%prep
-%setup
-
-%build
-
-# DO NOT use % { configure } , it hardcodes all paths, runs libtool,
-# so we can't do make prefix=/tmp/ install.
-
-# In fact, do not take out the spaces between % and { in the above comment,
-# because RPM will gladly do a substitution anyway.
-
-./configure --disable-checking --prefix=%{_prefix} --enable-optimise
-
-make all
-
-# make info
-make -C Documentation
-
-# make html
-make web-doc top-web
-
-%install
-
-
-rm -rf $RPM_BUILD_ROOT
-mkdir -p $RPM_BUILD_ROOT/tmp/lilypond-rpm-doc
-
-strip lily/out/lilypond midi2ly/out/midi2ly
-make prefix="$RPM_BUILD_ROOT%{_prefix}" install
-
-%if info=="yes"
-gzip -9fn $RPM_BUILD_ROOT%{_prefix}/info/*
-%endif
-
-mkdir -p $RPM_BUILD_ROOT/usr/share/emacs/site-lisp/site-start.d
-install -m 644 lilypond-mode.el lilypond-font-lock.el $RPM_BUILD_ROOT/usr/share/emacs/site-lisp/
-install -m 644 lilypond-init.el $RPM_BUILD_ROOT/usr/share/emacs/site-lisp/site-start.d
-
-gzip -9fn $RPM_BUILD_ROOT%{_prefix}/man/man1/*
-
-mkdir -p $RPM_BUILD_ROOT%{_prefix}/../etc/profile.d
-cp buildscripts/out/lilypond-profile $RPM_BUILD_ROOT%{_prefix}/../etc/profile.d/lilypond.sh
-cp buildscripts/out/lilypond-login $RPM_BUILD_ROOT%{_prefix}/../etc/profile.d/lilypond.csh
-
-
-# again, make sure that main package installs even if doco fails
-mkdir -p web/out
-tar -C web -xzf out/web.tar.gz
-
-
-%post
-
-touch /tmp/.lilypond-install
-rm `find /var/lib/texmf -name 'feta*pk -print' -or -name 'feta*tfm -print'` /tmp/.lilypond-install
-
-%if info=="yes"
-/sbin/install-info %{_prefix}/info/lilypond.info.gz %{_prefix}/info/dir
-%endif
-
-%preun
-
-%if info=="yes"
-if [ $1 = 0 ]; then
- /sbin/install-info --delete %{_prefix}/info/lilypond.info.gz %{_prefix}/info/dir
-fi
-%endif
-
-
-%files
-
-%{_datadir}/emacs/site-lisp/lilypond-*
-%{_datadir}/emacs/site-lisp/site-start.d/lilypond-*
-
-%{_prefix}/bin/abc2ly
-%{_prefix}/bin/as2text
-%{_prefix}/bin/convert-ly
-%{_prefix}/bin/etf2ly
-%{_prefix}/bin/lilypond
-%{_prefix}/bin/ly2dvi
-%{_prefix}/bin/midi2ly
-%{_prefix}/bin/lilypond-book
-%{_prefix}/bin/mup2ly
-%{_prefix}/bin/musedata2ly
-%{_prefix}/bin/pmx2ly
-
-%if info=="yes"
-%{_prefix}/info/lilypond.info.gz
-%{_prefix}/info/lilypond-internals.info.gz
-%endif
-
-%{_prefix}/man/man1/abc2ly.1.gz
-%{_prefix}/man/man1/as2text.1.gz
-%{_prefix}/man/man1/convert-ly.1.gz
-%{_prefix}/man/man1/etf2ly.1.gz
-%{_prefix}/man/man1/lilypond.1.gz
-%{_prefix}/man/man1/ly2dvi.1.gz
-%{_prefix}/man/man1/midi2ly.1.gz
-%{_prefix}/man/man1/lilypond-book.1.gz
-%{_prefix}/man/man1/musedata2ly.1.gz
-%{_prefix}/man/man1/mup2ly.1.gz
-%{_prefix}/man/man1/pmx2ly.1.gz
-
-%{_prefix}/share/lilypond/
-%{_prefix}/share/locale/*/LC_MESSAGES/lilypond.mo
-%{_prefix}/../etc/profile.d/lilypond.*
-
-%files documentation
-%doc web/
+++ /dev/null
-#
-# spec file for package lilypond (Version 1.3.149)
-# based on
-# spec file for package lilypond (Version 1.2.17)
-# Copyright (c) 2000 SuSE GmbH Nuernberg, Germany.
-#
-# Please send bug reports to schlemme@mathe.tu-freiberg.de
-
-%define info yes
-
-# neededforbuild guile tcsh tetex te_latex te_mpost libpng python gpp libgpp gettext autoconf netpbm libnetpb gs_serv gs_lib gs_fonts guile
-# usedforbuild aaa_base aaa_dir autoconf automake base bash bindutil binutils bison bzip compress cpio cracklib devs diff ext2fs file fileutil find flex gawk gcc gdbm gettext gpm gpp gppshare groff gs_fonts gs_lib gs_serv guile gzip kbd less libc libgpp libnetpb libpng libtool libz lx_suse make mktemp modules ncurses net_tool netcfg netpbm nkita nkitb nssv1 pam patch perl pgp ps python rcs rpm sendmail sh_utils shadow shlibs strace syslogd sysvinit tcsh te_ams te_latex te_mpost tetex texinfo textutil timezone unzip util vim xdevel xf86 xshared guile
-
-
-Distribution: SuSE Linux 7.0 (i386)
-Name: lilypond
-Version: @TOPLEVEL_VERSION@
-Release: 2
-Copyright: GPL
-Group: Applications/Publishing
-Source0: ftp.cs.uu.nl:/pub/GNU/LilyPond/development/lilypond-@TOPLEVEL_VERSION@.tar.gz
-# music notation software for.. ?
-Summary: A program for printing sheet music.
-URL: http://www.lilypond.org/
-# rpm: 4.0: broken for -ta builds: rpm doesn't look in tarball for xpm
-# Icon: lilypond-icon.xpm
-BuildRoot: /tmp/lilypond-install
-# add lots of Buildreq: tetex-kpath, te_mpost, bison
-# better prereqs: tetex-latex, python, (mpost?) etc.
-Prereq: tetex python
-
-# use keywords: music notation software
-%description
-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.
-
-Authors:
---------
- Han-Wen Nienhuys <hanwen@cs.uu.nl>
- Jan Nieuwenhuizen <janneke@gnu.org>
- Alexandre Oliva <oliva@dcc.unicamp.br>
- Mats Bengtsson <matsb@s3.kth.se>
- Eric Bullinger <eric@aut.ee.ethz.ch>
- Jan Arne Fagertun <Jan.A.Fagertun@energy.sintef.no>
- Anthony Fok <foka@debian.org>
- Neil Jerram <nj104@cus.cam.ac.uk>
- Donald Ervin Knuth
- Werner Lemberg <wl@gnu.org>
- David R. Linn <drl@vuse.vanderbilt.edu>
- François Pinard <pinard@iro.umontreal.ca>
- Jeffrey B. Reed <daboys@bga.com>
- Shay Rojanski
- Tom Cato Amundsen <tca@gnu.org>
- Laura Conrad <lconrad@world.std.com>
- James Hammons <jlhamm@pacificnet.net>
- Bjoern Jacke <bjoern.jacke@gmx.de>
- Michael Krause <m.krause@tu-harburg.de>
- David R. Linn <drl@vuse.vanderbilt.edu>
- Adrian Mariano
- Stephen Peters <portnoy@ai.mit.edu>
- Glen Prideaux <glenprideaux@iname.com>
- Roy R. Rankin <Roy.Rankin@alcatel.com.au>
- Juergen Reuter <reuterj@ira.uka.de>
- August S.Sigov <august@infran.ru>
- Rune Zedeler <rune@zedeler.dk>
-
-SuSE series: ap
-
-%package doc
-Summary: Prebuilt website containing all LilyPond documentation.
-Group: Applications/Publishing
-# BuildArchitectures: noarch
-
-%description doc
-
-The documentation of LilyPond, both in HTML and PostScript.
-
-%define INSTALL install -m755 -s
-%define INSTALL_DIR install -d -m755
-%define INSTALL_DATA install -m644
-%prep
-%setup
-
-%build
-
-#
-
-# DO NOT use % { configure } , it hardcodes all paths, runs libtool,
-# so we can't do make prefix=/tmp/ install.
-
-# In fact, do not take out the spaces between % and { , because RPM will gladly
-# do a substitution anyway.
-
-CFLAGS="$RPM_OPT_FLAGS" ./configure --disable-checking --disable-debugging --enable-printing --prefix=%{_prefix} --enable-optimise --enable-shared
-
-make LDFLAGS=-s "CFLAGS=$RPM_OPT_FLAGS" all
-
-# urg
-# %build doc
-# line 42: second %build
-# ok, now make sure that lilypond package will succeed,
-# even if documentation fails to build
-
-make -C Documentation || true
-make web-doc top-web || true
-
-%install
-
-
-
-rm -rf $RPM_BUILD_ROOT
-mkdir -p $RPM_BUILD_ROOT/tmp/lilypond-rpm-doc
-
-## this is an ugly hack
-mkdir -p scripts/share/lilypond/tex
-cp tex/titledefs.tex scripts/share/lilypond/tex
-## end of hack
-
-
-strip lily/out/lilypond midi2ly/out/midi2ly
-make prefix="$RPM_BUILD_ROOT%{_prefix}" install
-
-%{INSTALL_DIR} $RPM_BUILD_ROOT/usr/share/texmf/fonts/source/public/lilypond
-(cd $RPM_BUILD_ROOT/usr/share/lilypond \
- && mv mf/* $RPM_BUILD_ROOT/usr/share/texmf/fonts/source/public/lilypond \
- && rm -fr mf \
- && ln -s ../texmf/fonts/source/public/lilypond mf)
-%{INSTALL_DIR} $RPM_BUILD_ROOT/usr/share/texmf/fonts/afm/lilypond
-(cd $RPM_BUILD_ROOT/usr/share/lilypond \
- && mv afm/* $RPM_BUILD_ROOT/usr/share/texmf/fonts/afm/lilypond \
- && rm -fr afm \
- && ln -s ../texmf/fonts/afm/lilypond afm)
-%{INSTALL_DIR} $RPM_BUILD_ROOT/usr/share/texmf/tex/lilypond
-(cd $RPM_BUILD_ROOT/usr/share/lilypond \
- && mv tex/* $RPM_BUILD_ROOT/usr/share/texmf/tex/lilypond \
- && rm -fr tex \
- && ln -s ../texmf/tex/lilypond tex)
-%{INSTALL_DIR} $RPM_BUILD_ROOT/usr/share/texmf/lilypond/ps
-(cd $RPM_BUILD_ROOT/usr/share/lilypond \
- && mv ps/* $RPM_BUILD_ROOT/usr/share/texmf/lilypond/ps \
- && rm -fr ps \
- && ln -s ../texmf/lilypond/ps ps)
-
-
-%if info=="yes"
-gzip -9fn $RPM_BUILD_ROOT%{_prefix}/info/* || true
-%endif
-
-
-
-gzip -9fn $RPM_BUILD_ROOT%{_prefix}/man/man1/* || true
-
-
-
-
-mkdir -p $RPM_BUILD_ROOT%{_prefix}/../etc/profile.d
-cp buildscripts/out/lilypond-profile $RPM_BUILD_ROOT%{_prefix}/../etc/profile.d/lilypond.sh
-cp buildscripts/out/lilypond-login $RPM_BUILD_ROOT%{_prefix}/../etc/profile.d/lilypond.csh
-
-# urg
-#%install doc
-#line 63: second %install
-# again, make sure that main package installs even if doco fails
-mkdir -p web/out
-tar -C web -xzf out/web.tar.gz || true
-
-%ifos cygwin
-# urg, this symlink doesn't come through on cygwin
-# this is the way symlinks work over there, let's fake one
-rm -f $RPM_BUILD_ROOT%{_prefix}/share/lilypond/cmtfm
-echo '!<symlink>c:\\texmf\\fonts\\tfm\\public\\cm' > $RPM_BUILD_ROOT%{_prefix}/share/lilypond/cmtfm
-%{fix_suffixes}
-%endif
-
-%{?suse_check}
-
-
-%pre
-if [ -d usr/share/lilypond/ps ]; then
- mv usr/share/lilypond/ps usr/share/lilypond/ps.old
- echo "please, remove /usr/share/lilypond/ps.old manually."
-fi
-
-%post
-
-touch /tmp/.lilypond-install
-rm `find /var/lib/texmf -name 'feta*pk -print' -or -name 'feta*tfm -print'` /tmp/.lilypond-install
-%if info=="yes"
-/usr/bin/install-info %{_prefix}/info/lilypond.info.gz %{_prefix}/info/dir || true
-%endif
-mkdir -p var/adm/SuSEconfig
-touch var/adm/SuSEconfig/run-texhash
-
-
-%preun
-%if info=="yes"
-if [ $1 = 0 ]; then
- /usr/bin/install-info --delete %{_prefix}/info/lilypond.info.gz %{_prefix}/info/dir || true
-fi
-%endif
-
-%postun
-mkdir -p var/adm/SuSEconfig
-touch var/adm/SuSEconfig/run-texhash
-
-
-
-%files
-%defattr(-, root, root)
-%doc CHANGES COPYING DEDICATION INSTALL.txt NEWS
-%doc README.txt FAQ.txt AUTHORS.txt VERSION ROADMAP
-%doc buildscripts/
-%doc scripts/
-# hairy to hook it in (possibly non-existing) emacs
-%doc lilypond-mode.el
-%doc lilypond-font-lock.el
-
-%config /etc/profile.d/*
-
-%ifnos cygwin
-%{_prefix}/bin/abc2ly
-%{_prefix}/bin/as2text
-%{_prefix}/bin/convert-ly
-%{_prefix}/bin/etf2ly
-%{_prefix}/bin/lilypond
-%{_prefix}/bin/ly2dvi
-%{_prefix}/bin/midi2ly
-%{_prefix}/bin/lilypond-book
-%{_prefix}/bin/mup2ly
-%{_prefix}/bin/musedata2ly
-%{_prefix}/bin/pmx2ly
-%else
-%{_prefix}/bin
-%endif
-
-%if info=="yes"
-%{_prefix}/info/lilypond.info.gz
-%{_prefix}/info/lilypond-internals.info.gz
-%endif
-
-%{_prefix}/man/man1/abc2ly.1.gz
-%{_prefix}/man/man1/as2text.1.gz
-%{_prefix}/man/man1/convert-ly.1.gz
-%{_prefix}/man/man1/etf2ly.1.gz
-%{_prefix}/man/man1/lilypond.1.gz
-%{_prefix}/man/man1/ly2dvi.1.gz
-%{_prefix}/man/man1/midi2ly.1.gz
-%{_prefix}/man/man1/lilypond-book.1.gz
-%{_prefix}/man/man1/musedata2ly.1.gz
-%{_prefix}/man/man1/mup2ly.1.gz
-%{_prefix}/man/man1/pmx2ly.1.gz
-
-%{_prefix}/share/lilypond/
-%{_prefix}/share/texmf/
-%{_prefix}/share/locale/*/LC_MESSAGES/lilypond.mo
-# urg?
-#%{_prefix}/../etc/profile.d/lilypond.*
-
-%files doc
-# this gets too messy...
-%doc mutopia/
-%doc input/
-%doc web/
-# verbatim include of input: list the directory without issuing a %dir
-
-%changelog -n lilypond
-* Sun Apr 22 2001 - schlemme@mathe.tu-freiberg.de
-- update: 1.3.149
-* Mon Apr 10 2000 - bk@suse.de
-- added suse update config macro
-* Thu Mar 16 2000 - kukuk@suse.de
-- Use gs_serv, not gs_both (doesn't exist on all platforms)
-* Wed Mar 01 2000 - uli@suse.de
-- moved man pages to /usr/share
-* Tue Dec 21 1999 - ke@suse.de
-- add documentation (#271).
-* Mon Dec 13 1999 - ke@suse.de
-- update: 1.2.17.
-- compiler fix (thanks to schwab@suse.de).
-- #271.
-* Mon Oct 25 1999 - ke@suse.de
-- update: 1.2.16.
-* Mon Sep 13 1999 - bs@suse.de
-- ran old prepare_spec on spec file to switch to new prepare_spec.
-* Mon Sep 06 1999 - ro@suse.de
-- update to 1.2.6 to make it compile with new guile
-- various fixes and one hack to make this compile at all
-* Sun Aug 22 1999 - ke@suse.de
-- provide /etc/profile.d scripts.
-- make lily.ps available (thanks to Ulrich Windl).
-* Tue Aug 17 1999 - ke@suse.de
-- update: version 1.2.1.
-* Thu Nov 05 1998 - ke@suse.de
-- use the TDS and provide links from /usr/share/lilypond.
-- install examples via %doc.
-* Wed Oct 28 1998 - ke@suse.de
-- update: version 1.0.17.
-* Fri Aug 07 1998 - ke@suse.de
-- initial package: version 1.0.0
projects / lilypond.git / commitdiff