summaryrefslogtreecommitdiff
blob: c591cd42ec0dce1244a3fe634e9b6776876658bb (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
# ChangeLog for dev-ruby/ruby-gtk
# Copyright 2002-2004 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-ruby/ruby-gtk/ChangeLog,v 1.11 2004/01/09 14:48:31 agriffis Exp $

  09 Jan 2004; Aron Griffis <agriffis@gentoo.org> ruby-gtk-0.34-r1.ebuild:
  stable on alpha

  26 Dec 2003; Jason Wever <weeve@gentoo.org> ruby-gtk-0.34-r1.ebuild:
  Added ~sparc keyword.

*ruby-gtk-0.34-r1 (12 Dec 2003)

  12 Dec 2003; Mamoru KOMACHI <usata@gentoo.org> ruby-gtk-0.34-r1.ebuild:
  inherit ruby to support both ruby16 and ruby18

*ruby-gtk-0.34 (21 Jul 2003)

	21 Jul 2003; Tom Payne <twp@gentoo.org> ruby-gtk-0.34.ebuild :
	Version bump.

*ruby-gtk-0.30 (07 Jan 2003)

	07 Jan 2003; Aron Griffis <agriffis@gentoo.org> ruby-gtk-0.30.ebuild:
	Update from 0.29 to 0.30.  Add ~alpha to KEYWORDS.

*ruby-gtk-0.29 (06 Jul 2002)

	06 Jul 2002; Aron Griffis <agriffis@gentoo.org> ruby-gtk-0.29.ebuild :

	Updated to version 0.29.  Added SLOT and LICENSE.

	07 Jul 2002; Aron Griffis <agriffis@gentoo.org> ruby-gtk-0.29.ebuild :

	Added KEYWORDS.

*ruby-gtk-0.27 (13 Apr 2002)

	13 Apr 2002; Seemant Kulleen <seemant@gentoo.org> ruby-gtk-0.27.ebuild :

	thomharp@charter.net submitted this updated ebuild in bug #1647.  I have
	cleaned it up slightly to allow future updates to be more flexible.
	However, why did the ruby-gtk (ruby-gnome) people have to change the
	naming convention?

	07 Jul 2002; Aron Griffis <agriffis@gentoo.org> ruby-gtk-0.27.ebuild :

	Added LICENSE, KEYWORDS, SLOT.

*ruby-gtk-0.26 (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.