dev-ruby/amstd/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
56
57
58
59
60
61
62

# ChangeLog for dev-ruby/amstd
# Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-ruby/amstd/ChangeLog,v 1.17 2004/11/13 02:04:58 kumba Exp $

  12 Nov 2004; Joshua Kinard <kumba@gentoo.org> amstd-2.0.0-r1.ebuild:
  Marked stable on mips.

  01 Nov 2004; Markus Rothe <corsair@gentoo.org>

  amstd-2.0.0-r1.ebuild:
  Marked ~ppc64; bug #67098

  10 Oct 2004; Simon Stelling <blubb@gentoo.org> amstd-2.0.0-r1.ebuild:
  added ~amd64

  03 Oct 2004; Mamoru KOMACHI <usata@gentoo.org> amstd-2.0.0-r1.ebuild:
  Stable on ppc.

  15 Apr 2004; Ciaran McCreesh <ciaranm@gentoo.org> amstd-2.0.0-r1.ebuild:
  Sparc stable

  13 Apr 2004; Guy Martin <gmsoft@gentoo.org> amstd-2.0.0-r1.ebuild:
  Marked stable on hppa.

  10 Apr 2004; David Holm <dholm@gentoo.org> amstd-2.0.0-r1.ebuild:
  Added to ~ppc.

  10 Apr 2004; Mamoru KOMACHI <usata@gentoo.org> amstd-2.0.0-r1.ebuild,
  amstd-2.0.0.ebuild:
  virtual/ruby fix

*amstd-2.0.0-r1 (16 Nov 2003)

*amstd-2.0.0 (07 Jan 2003)

  23 May 2003; Tom Payne <twp@gentoo.org> amstd-2.0.0.ebuild :
  Added IUSE.

  12 May 2003; Tom Payne <twp@gentoo.org> amstd-2.0.0.ebuild :
  Marked as stable on all ARCHes. Ebuild and ChangeLog tidying.

  07 Jan 2003; Aron Griffis <agriffis@gentoo.org> amstd-2.0.0.ebuild :
  Update to latest version

  07 Jan 2003; Chris Houser <chouser@gentoo.org> amstd-1.9.5.ebuild :
  Added "alpha" to KEYWORDS

  07 Jul 2002; Aron Griffis <agriffis@gentoo.org> amstd-1.9.5.ebuild :
  Updated with LICENSE, KEYWORDS, SLOT.

*amstd-1.9.5 (1 Feb 2002)

  12 May 2003; Tom Payne <twp@gentoo.org> :
  Removed old version.

  01 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.