dev-perl/PlRPC/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
62

# ChangeLog for dev-perl/PlRPC
# Copyright 2002-2005 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-perl/PlRPC/ChangeLog,v 1.18 2005/04/29 01:58:27 mcummings Exp $

*PlRPC-0.2018 (29 Apr 2005)

  29 Apr 2005; Michael Cummings <mcummings@gentoo.org> -PlRPC-0.2016.ebuild,
  +PlRPC-0.2018.ebuild:
  cleaning for mirror syntax

  01 Jun 2004; Tom Gall <tgall@gentoo.org> PlRPC-0.2016-r1.ebuild:
  stable on ppc64, bug #52701

  02 Apr 2004; <randy@gentoo.org> PlRPC-0.2016-r1.ebuild:
  adding s390 keywords

  21 Mar 2004; Joshua Kinard <kumba@gentoo.org> PlRPC-0.2016-r1.ebuild:
  Marked stable on mips.

  04 Feb 2004; Joshua Kinard <kumba@gentoo.org> PlRPC-0.2016-r1.ebuild:
  Added ~mips to KEYWORDS

*PlRPC-0.2016-r1 (29 Oct 2002)

  05 Apr 2003; Zach Welch <zwelch@gentoo.org> PlRPC-0.2016-r1.ebuild:
  add arm keyword

  20 Mar 2003; Guy Martin <gmsoft@gentoo.org> PlRPC-0.2016-r1.ebuild : 
  Added hppa to KEYWORDS.

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : 
  changed sparc ~sparc keywords
 
  31 Oct 2002; <mcummings@gentoo.org> : 
  added keywords sparc sparc64

  29 Oct 2002; Seemant Kulleen <seemant@gentoo.org> ChangeLog  :
  forced version bump to install into correct locations

*PlRPC-0.2016 (8 Sep 2002)

  8 Sep 2002; <mcummings@gentoo.org> PlRPC-0.2016.ebuild:
  Version bump to correct bugs

*PlRPC-0.2014-r1 (5 May 2002)

  31 Jul 2002; Calum Selkirk <cselkirk@gentoo.org> PlRPC-0.2014-r1.ebuild :
  Added ppc to KEYWORDS.

  5 May 2002; Seemant Kulleen <seemant@gentoo.org> PlRPC-0.2014-r1.ebuild
  files/digest-PlRPC-0.2014-r1 :
  eclassed.

*PlRPC-0.2014 (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.