summaryrefslogtreecommitdiff
blob: 505ecf12066fe7509a1aefccda9cb09d7ab79161 (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
# ChangeLog for x11-wm/oroborus-extras
# Copyright 2002-2007 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/x11-wm/oroborus-extras/ChangeLog,v 1.15 2007/02/06 02:10:36 flameeyes Exp $

  06 Feb 2007; Diego Pettenò <flameeyes@gentoo.org> ChangeLog:
  Regenerate digest in Manifest2 format.

  08 May 2005; Herbie Hopkins <herbs@gentoo.org>
  oroborus-extras-2.0.13.ebuild:
  Stable on amd64.

  07 Mar 2005; Gustavo Zacarias <gustavoz@gentoo.org>
  oroborus-extras-2.0.13.ebuild:
  Stable on sparc

  03 Jul 2004; Tom Martin <slarti@gentoo.org> oroborus-extras-2.0.13.ebuild:
  Added to ~amd64.

  07 May 2004; Brandon Hale <tseng@gentoo.org>
  oroborus-extras-2.0.1-r1.ebuild:
  Add IUSE=

  27 Apr 2004; Aron Griffis <agriffis@gentoo.org>
  oroborus-extras-2.0.13.ebuild:
  Add inherit eutils

  08 Dec 2003; Mike Gardiner <obz@gentoo.org> oroborus-extras-2.0.13.ebuild,
  files/deskmenu-1.4.0-string.patch:
  Patched for multi-line string (help function), see bug #35030. Reported
  upstream via email

*oroborus-extras-2.0.13 (09 Jul 2003)

  09 Jul 2003; Martin Holzer <mholzer@gentoo.org>
  oroborus-extras-2.0.13.ebuild:
  Version bumped. ebuild submitted by Soren Harward <soren@byu.edu> in #23780.

  12 Jun 2003; <msterret@gentoo.org> oroborus-extras-2.0.1-r1.ebuild:
  add Header

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*oroborus-extras-2.0.1-r1 (09 Apr 2002)
  9 Apr 2002; Spider <spider@gentoo.org>
  Add an update to depend on  =x11-libs/gtk+-1.2*
  No need in upping the -r for an dependency
  
*oroborus-extras-2.0.1-r1 (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.