summaryrefslogtreecommitdiff
blob: 3a6a093861ccbd56c5c9df8e657d63c4fcc333f5 (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
# ChangeLog for dev-tcltk/expect
# Copyright 2002-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-tcltk/expect/ChangeLog,v 1.11 2003/03/14 08:23:54 george Exp $

*expect-5.37.1-r1 (20 Jul 2002)

  13 Mar 2003; George Shapovalov <george@gentoo.org> epect-5.33.0.ebuild :
  well, this version is really old, but since it is only second one awailable in portage,
  leaving it in so far. Cleaned it up somewhat, adjusted KEYWORDS..
  
  10 Mar 2003; Aron Griffis <agriffis@gentoo.org> expect-5.37.1-r1.ebuild:
  Mark stable on alpha

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

  27 Oct 2002; George Shapovalov <george@gentoo.org> expect-5.37.1-r1.ebuild,
  expect-5.37.1-r2.ebuild :
  incorporated changes in -r2 into -r1 and deleted -r2 keeping -r1 unmasked.
  Avoiding revision bump in unmasked version, since the fix will only concern
  some users.

  25 Oct 2002; George Shapovalov <george@gentoo.org> expect-5.37.1-r2.ebuild :
  modified src_install to add examples if doc is defined. 
  Revision bumped for testing.

  23 Sep 2002; Olivier Reisch <doctomoe@gentoo.org> expect-5.37.1-r1.ebuild:
  Added ppc keyword

  20 Jul 2002; George Shapovalov <george@gentoo.org> expect-5.37.1-r1.ebuild :
  modified ebuild to install shared libraries (necessary for multixterm)
  upping revision to force-update.

*expect-5.37.1 (08 July 2002)

  08 July 2002; George Shapovalov <george@gentoo.org> expect-5.37.1.ebuild :
  upped version, + some cleaning up.
  removed Author line, original ebuild by Tod Neidt <tneidt@fidnet.com>

*expect-5.33.0 (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.