Hello community,

here is the log from the commit of package lilypond for openSUSE:Factory 
checked in at 2012-07-24 22:42:51
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/lilypond (Old)
 and      /work/SRC/openSUSE:Factory/.lilypond.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "lilypond", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/lilypond/lilypond.changes        2012-07-03 
14:25:57.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.lilypond.new/lilypond.changes   2012-07-24 
22:42:53.000000000 +0200
@@ -1,0 +2,5 @@
+Tue Jul 24 09:07:09 UTC 2012 - [email protected]
+
+- Make if build with latest TeXLive 2012 
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ lilypond.spec ++++++
--- /var/tmp/diff_new_pack.dHP9WK/_old  2012-07-24 22:42:54.000000000 +0200
+++ /var/tmp/diff_new_pack.dHP9WK/_new  2012-07-24 22:42:54.000000000 +0200
@@ -22,8 +22,8 @@
 Name:           lilypond
 Version:        2.15.40
 Release:        0
-License:        GPL-3.0+
 Summary:        A typesetting system for music notation
+License:        GPL-3.0+
 Group:          Productivity/Publishing
 
 Url:            http://www.lilypond.org
@@ -54,11 +54,20 @@
 BuildRequires:  t1utils
 BuildRequires:  texi2html
 BuildRequires:  texinfo >= 4.8
+%if %suse_version > 1220
+BuildRequires:  dblatex
+BuildRequires:  makeinfo
+BuildRequires:  texlive-extratools
+BuildRequires:  texlive-latex
+BuildRequires:  texlive-metafont
+BuildRequires:  texlive-metapost
+%else
 BuildRequires:  texlive
 BuildRequires:  texlive-bin
 BuildRequires:  texlive-bin-tools
 BuildRequires:  texlive-latex
 BuildRequires:  texlive-metapost
+%endif
 BuildRequires:  vim-base
 BuildRequires:  zip
 BuildRequires:  pkgconfig(pango) >= 1.12.0

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to