x11-plugins/wmCalClock/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

# ChangeLog for x11-plugins/wmCalClock
# Copyright 2002-2006 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/x11-plugins/wmCalClock/ChangeLog,v 1.13 2006/01/22 11:31:03 nelchael Exp $

  22 Jan 2006; Krzysiek Pawlik <nelchael@gentoo.org>
  wmCalClock-1.25-r1.ebuild:
  Fixed DEPEND for modular X.

  10 Nov 2005; Michele Noberasco <s4t4n@gentoo.org> wmCalClock-1.25-r1.ebuild:
  Removed COPYING and INSTALL from dodoc.

  13 Sep 2005; Michele Noberasco <s4t4n@gentoo.org> wmCalClock-1.25-r1.ebuild:
  Added some magic sed to remove unneeded SYSTEM variable from Makefile,
  fixing bug #105730.

  31 Aug 2004; Tom Gall <tgall@gentoo.org> wmCalClock-1.25-r1.ebuild:
  stable on ppc64, bug #61761

  20 Jul 2004; Michele Noberasco <s4t4n@gentoo.org> wmCalClock-1.25-r1.ebuild:
  Fixed the ebuild so that it does actually produce a working binary.
  How on Earth is possible that this ebuild is stable for lots of arches
  while not even producing a binary?!? Closes #57123.
  wmCalClock-1.25-r1.ebuild:
  Wipe out old ebuilds...

  07 Mar 2004; Stephen P. Becker <geoman@gentoo.org>
  wmCalClock-1.25-r1.ebuild:
  Added ~mips keyword.

  17 Jun 2003; Will Woods <wwoods@gentoo.org> wmCalClock-1.25-r1.ebuild:
  Added alpha to KEYWORDS

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 

*wmCalClock-1.25-r1 (03 Nov 2002)

  03 Nov 2002; Seemant Kulleen <seemant@gentoo.org> wmCalClock-1.25-r1.ebuild
  files/digest-wmCalClock-1.25-r1 :

  Made FHS compliant and installed documentation

*wmCalClock-1.25 (1 Feb 2002)

  29 Aug 2002; Seemant Kulleen <seemant@gentoo.org> * :

  Relocated to x11-plugins

  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.