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
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
# ChangeLog for dev-libs/log4c
# Copyright 2002-2005 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-libs/log4c/ChangeLog,v 1.24 2005/01/03 16:00:45 gustavoz Exp $
03 Jan 2005; Gustavo Zacarias <gustavoz@gentoo.org> log4c-1.0.10-r1.ebuild:
Stable on sparc wrt #70529
02 Jan 2005; Daniel Black <dragonheart@gentoo.org>
files/log4c-1.0.10-nodocs.patch, log4c-1.0.10-r1.ebuild:
Fixed ebuild with no doc use flag as per patch from Lee Thompson
<bm55b@yahoo.com> in bug #70529.
04 Dec 2004; Daniel Black <dragonheart@gentoo.org> log4c-1.0.10-r1.ebuild,
log4c-1.0.11:
ppc keyword 1.0.10-r1. Note versions >=1.0.11 are package.masked due to config
file problems listed in bug #70529. ~x86 and ~sparc keyworded 1.0.11 due
to problems.
03 Dec 2004; Daniel Black <dragonheart@gentoo.org> log4c-1.0.10-r1.ebuild:
patched to fix selftest failure - bug #70529. Thanks Lee and Aaron
21 Nov 2004; Daniel Black <dragonheart@gentoo.org>
+files/log4c-1.0.11-function.patch, +files/log4c-1.0.12-function.patch,
log4c-1.0.11.ebuild, log4c-1.0.12.ebuild:
fixed test cases for 1.0.11 and 1.0.12. Patch courtesy of Olaf Freyer
<aaron@cs.tu-berlin.de> in bug #70529.
*log4c-1.0.10-r1 (20 Nov 2004)
20 Nov 2004; Daniel Black <dragonheart@gentoo.org>
+files/log4c-1.0.10-nodocs.patch, +log4c-1.0.10-r1.ebuild:
log4c-1.0.10-r1 added per bug #70529. Thanks to Lee Thompson <bm55b@yahoo.com>
28 Oct 2004; Simon Stelling <blubb@gentoo.org> log4c-1.0.12.ebuild:
added ~amd64
09 Oct 2004; Jason Wever <weeve@gentoo.org> log4c-1.0.11.ebuild:
Stable on sparc.
07 Sep 2004; Daniel Black <dragonheart@gentoo.org> log4c-1.0.6-r1.ebuild,
-log4c-1.0.6.ebuild:
old version cleanout. Fixed HOMEPAGE on old version.
*log4c-1.0.12 (07 Sep 2004)
07 Sep 2004; Daniel Black <dragonheart@gentoo.org> metadata.xml,
log4c-1.0.11.ebuild, +log4c-1.0.12.ebuild:
Version bump as per bug #62859. I'm taking over maitaince - ref metadata.xml.
Marked 1.0.11 x86 stable. Reintroduced sparc and ppc keywords to 1.0.11.
Thanks to Olaf Freyer <aaron@cs.tu-berlin.de> for the good bug report
12 Aug 2004; Daniel Black <dragonheart@gentoo.org>
+files/log4c_1.0.11_test.patch, +files/makefile.doc.am.patch,
files/makefile.doc.in.patch, log4c-1.0.11.ebuild:
fixed access violation. Fixed to compile with gcc 3.4 thanks to patch by Olaf
Freyer <aaron@cs.tu-berlin.de> in bug #60061
11 Aug 2004; Daniel Black <dragonheart@gentoo.org>
+files/makefile.doc.in.patch, log4c-1.0.11.ebuild:
Fixes thank to Aaron Walker <ka0ttic@butsugenjitemple.org> in bug #60047
*log4c-1.0.11 (11 Aug 2004)
11 Aug 2004; Daniel Black <dragonheart@gentoo.org> +metadata.xml,
+log4c-1.0.11.ebuild, +files/configure.in.patch:
Version bump thanks to Aaron Walker <ka0ttic@butsugenjitemple.org> in bug
#59666.
18 May 2004; Mamoru KOMACHI <usata@gentoo.org> log4c-1.0.6-r1.ebuild,
log4c-1.0.6.ebuild:
Changed app-text/tetex to virtual/tetex.
04 Apr 2004; Lars Weiler <pylon@gentoo.org> log4c-1.0.6-r1.ebuild:
stable on ppc
14 Mar 2004; Michael Sterrett <mr_bones_@gentoo.org> log4c-1.0.6-r1.ebuild,
log4c-1.0.6.ebuild:
Don't assign default to S; header fix
22 Feb 2004; David Holm <dholm@gentoo.org> log4c-1.0.6-r1.ebuild:
Added to ~ppc.
06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
*log4c-1.0.6-r1 (20 Jun 2002)
20 Jun 2002; Matthew Kennedy <mkennedy@gentoo.org> ChangeLog,
log4c-1.0.6-r1.ebuild, files/digest-log4c-1.0.6-r1 :
Fixed tetex sandbox violation. General lintool clean-up.
*log4c-1.0.6 (2 May 2002)
2 May 2002; Matthew Kennedy <mkennedy@gentoo.org> ChangeLog,
log4c-1.0.6.ebuild, files/digest-log4c-1.0.6 :
New ebuild.
Log4c is a library of C for flexible logging to files, syslog and
other destinations. It is modeled after the Log for Java library
(http://jakarta.apache.org/log4j/), staying as close to their API as
is reasonable.
|