blob: 77d84f033d34f75b769cdf53e2d6591f4321a5a3 (
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
60
61
62
63
64
65
66
|
# ChangeLog for dev-util/pccts
# Copyright 2002-2004 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-util/pccts/ChangeLog,v 1.14 2004/03/12 20:32:57 gustavoz Exp $
12 Mar 2004; Gustavo Zacarias <gustavoz@gentoo.org> pccts-1.33.33.ebuild:
stable on sparc
29 Jan 2004; <agriffis@gentoo.org> pccts-1.33.33.ebuild:
stable on alpha and ia64
26 Oct 2003; Brad House <brad_mssw@gentoo.org> pccts-1.33.33.ebuild:
add amd64 flag
*pccts-1.33.33 (11 Jun 2003)
11 Jul 2003; Guy Martin <gmsoft@gentoo.org> pccts-1.33.33.ebuild :
Added hppa to KEYWORDS.
11 Jun 2003; Patrick Kursawe <phosphan@gentoo.org> pccts-1.33.33.ebuild,
files/pccts-1.33.33-gentoo.diff:
Bumping to maintainance release .33
23 May 2003; Patrick Kursawe <phosphan@gentoo.org>
files/pccts-1.33.32-r1-gentoo.diff:
Updated the patch for some gcc3.3 compile problem (bug 21528) - no revision
bump necessary.
06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
*pccts-1.33.32-r1 ( 17 Mar 2002 )
23 Jul 2002; Mark Guertin <gerk@gentoo.org> :
Added ppc to keywords
17 Mar 2002; G.Bevin <gbevin@gentoo.org> pccts-1.33.32-r1.ebuild
files/digest-pccts-1.33.32-r1
Fixed wrong sorcerer include path.
*pccts-1.33.32 ( 15 Mar 2002 )
15 Mar 2002; G.Bevin <gbevin@gentoo.org> pccts-1.33.32.ebuild
files/digest-pccts-1.33.32 files/pccts-1.33.32-gentoo.diff
New upstream version.
Old versions removed.
*pccts-1.33.31 ( 12 Feb 2002 )
12 Feb 2002; Karl Trygve Kalleberg <karltk@gentoo.org> pccts-1.33.31.ebuild
files/digest-pccts-1.33.31
New upstream version.
Old versions removed.
*pccts-1.33.24-r2 (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.
|