media-sound/lilypond/ChangeLog


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

# ChangeLog for media-sound/lilypond
# Copyright 2002-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/media-sound/lilypond/ChangeLog,v 1.11 2003/09/12 16:48:26 agriffis Exp $

  12 Sep 2003; Aron Griffis <agriffis@gentoo.org> lilypond-1.6.9.ebuild:
  Remove web-doc building since it's broken in this ebuild and the 1.8.0 ebuild
  will have it fixed. This finishes bug 21305

  12 Sep 2003; Aron Griffis <agriffis@gentoo.org> lilypond-1.6.9.ebuild:
  Fix (part of) bug 21305 by disabling ccache.

  27 May 2003; jje <jje@gentoo.org> lilypond-1.6.9.ebuild:
  Fixed web-doc target, die was missing...

*lilypond-1.6.9 (17 May 2003)

  17 May 2003; jje <jje@gentoo.org> lilypond-1.6.9.ebuild:
  Simplified src_compile to reflect current compiler usage.
  
  The web-doc target is also being built.

  18 Jan 2003; Aron Griffis <agriffis@gentoo.org> lilypond-1.6.6.ebuild :
  Fix bug 13396 by requiring tetex-1.0.7-r12 which should fix the missing
  mf.base compilation problem.

*lilypond-1.6.6 (03 Dec 2002)

  09 Mar 2003; Aron Griffis <agriffis@gentoo.org> lilypond-1.6.6.ebuild:
  Mark stable on alpha

  21 Feb 2003; Aron Griffis <agriffis@gentoo.org> lilypond-1.6.6.ebuild :
  Add ~alpha to KEYWORDS

  03 Dec 2002; Aron Griffis <agriffis@gentoo.org> lilypond-1.6.6.ebuild :

  Update to version 1.6.6 which compiles with at least gcc-2.95.3 and
  gcc-3.2.1.  I put clauses in the ebuild to help compile for gcc-3.[01] but
  haven't been able to test them.  It shouldn't matter (much) since Gentoo 1.2
  is using gcc-2.95.3 and Gentoo 1.4 is using gcc-3.2.  This fixes BUG #4682.
  Thanks to Mike Ossmann <mike@ossmann.com> for his work on this version.

*lilypond-1.5.15 (1 Feb 2002)

  1 Feb 2002; G.Bevin <gbevin@gentoo.org> ChangeLog :
  
  Added initial ChangeLog which should be updated whenever the package is
  updated in any way. This changelog is targetted to users. This means that the
  comments should well explained and written in clean English. The details about
  writing correct changelogs are explained in the skel.ChangeLog file which you
  can find in the root directory of the portage repository.