dev-perl/Parse-RecDescent/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
51
52
53
54
55
56
57
58
59
60
61

# ChangeLog for dev-perl/Parse-RecDescent
# Copyright 2002-2004 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-perl/Parse-RecDescent/ChangeLog,v 1.16 2004/03/07 05:15:46 geoman Exp $

  07 Mar 2004; Stephen P. Becker <geoman@gentoo.org>
  Parse-RecDescent-1.94.ebuild:
  Added ~mips keyword.

  07 Jan 2004; <gustavoz@gentoo.org> Parse-RecDescent-1.94.ebuild:
  marked stable on sparc

  24 Jun 2003; Aron Griffis <agriffis@gentoo.org>
  Parse-RecDescent-1.94.ebuild:
  Mark stable on alpha

*Parse-RecDescent-1.94 (31 May 2003)

  03 Jul 2003; Guy Martin <gmsoft@gentoo.org> Parse-RecDescent-1.94.ebuild :
  Added hppa to KEYWORDS.

  31 May 2003; Michael Cummings <mcummings@gentoo.org>
  Parse-RecDescent-1.94.ebuild:
  New version from CPAN
  Added missing DEPEND

  28 May 2003; Michael Cummings <mcummings@gentoo.org> : corrected 
  description of module to be a description, not 'Perl Module'

  Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
  29 Oct 2002; Seemant Kulleen <seemant@gentoo.org> ChangeLog  :
  forced version bump to install into correct locations

*Parse-RecDescent-1.80-r3 (21 Jun 2003)
 
  12 Jul 2003; Daniel Ahlberg <aliz@gentoo.org> :
  Added missing changelog entry.

*Parse-RecDescent-1.80-r2 (21 Jun 2003)
 
  12 Jul 2003; Daniel Ahlberg <aliz@gentoo.org> :
  Added missing changelog entry.

*Parse-RecDescent-1.80-r1 (27 Mar 2002)

  24 Jul 2002; Mark Guertin <gerk@gentoo.org> :
  Added ppc to keywords

  27 Mar 2002; Seemant Kulleen <seemant@gentoo.org> Parse-RecDescent-1.80-r1.ebuild :

  Ungzipped HTML documentation.

*Parse-RecDescent-1.80 (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.