summaryrefslogtreecommitdiff
blob: 119b0fe8a614ffc10508c6650abbf3dae8b0db07 (plain)
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
# ChangeLog for dev-perl/Period
# Copyright 2002-2007 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-perl/Period/ChangeLog,v 1.17 2007/01/19 15:20:26 mcummings Exp $

  19 Jan 2007; Michael Cummings <mcummings@gentoo.org>
  Period-1.20-r3.ebuild:
  Version bump, thanks seemant

  05 Aug 2006; Michael Cummings <mcummings@gentoo.org>
  Period-1.20-r3.ebuild:
  Adding perl dep; fixed header; fixed DEPEND

  02 Oct 2005; Aron Griffis <agriffis@gentoo.org> Period-1.20-r3.ebuild:
  Mark 1.20-r3 stable on ia64

  26 Aug 2005; Aron Griffis <agriffis@gentoo.org> Period-1.20-r3.ebuild:
  add ~ia64

  24 Apr 2005; Michael Cummings <mcummings@gentoo.org>
  -Period-1.20-r2.ebuild, Period-1.20-r3.ebuild:
  cleaning

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

  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

*Period-1.20-r2 (08 Jul 2002)

  31 Jul 2002; Calum Selkirk <cselkirk@gentoo.org> Period-1.20-r2.ebuild :

  Added ppc to KEYWORDS.

  08 Jul 2002; Phil Bordelon <sunflare@gentoo.org> Period-1.20-r2.ebuild

  The ebuild no longer worked with our current Perl modules system.  Fixed.
  I also lintool'd and repoman'd it while I was at it.

*Period-1.20-r1 (5 May 2002)

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

  eclassed

*Period-1.20 (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.