dev-perl/XML-Parser/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

# ChangeLog for dev-perl/XML-Parser
# Copyright 2002-2004 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-perl/XML-Parser/ChangeLog,v 1.16 2004/03/04 14:44:51 gustavoz Exp $

  04 Mar 2004; Gustavo Zacarias <gustavoz@gentoo.org> XML-Parser-2.34.ebuild:
  stable on sparc

  27 Feb 2004; Michael Cummings <mcummings@gentoo.org> XML-Parser-2.33.ebuild:
  Cleaning up

  27 Feb 2004; Michael Cummings <mcummings@gentoo.org> XML-Parser-2.34.ebuild:
  Unmasking for x86 after 87 days

  18 Jan 2004; <tuxus@gentoo.org> XML-Parser-2.31-r1.ebuild:
  Added ~mips to KEYWORDS.

  07 Jan 2004; <agriffis@gentoo.org> XML-Parser-2.34.ebuild:
  stable on alpha and ia64

*XML-Parser-2.34 (02 Dec 2003)

  02 Dec 2003; <max@gentoo.org> XML-Parser-2.34.ebuild:
  Bump to version 2.34.  Needed for xmltv-0.5.24

*XML-Parser-2.33 (31 Jul 2003)

  31 Jul 2003; Michael Cummings <mcummings@gentoo.org> XML-Parser-2.33.ebuild:
  CPAN Version bump;installs good, appears to be good, testing needed.

*XML-Parser-2.31-r1 (29 Oct 2002)

  16 Apr 2003; Guy Martin <gmsoft@gentoo.org> XML-Parser-2.31-r1.ebuild :
  Added hppa to KEYWORDS.

  06 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

*XML-Parser-2.31 (6 May 2002)

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

  6 May 2002; Seemant Kulleen <seemant@gentoo.org> XML-Parser-2.31.ebuild
  files/digest-XML-Parser-2.31 :

  Version update and conversion to eclass

*XML-Parser-2.30 (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.