dev-tcltk/itcl/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 dev-tcltk/itcl
# Copyright 2002-2004 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-tcltk/itcl/ChangeLog,v 1.13 2004/03/25 06:29:11 weeve Exp $

  24 Mar 2004; Jason Wever <weeve@gentoo.org> itcl-3.2.1.ebuild:
  Stable on sparc.

  08 Mar 2004; Robin Johnson,,604-339-5621,604-298-8414 <robbat2@gentoo.org>
  itcl-3.2.1-r1.ebuild:
  fix bug 44022, editing glitch

*itcl-3.2.1-r1 (07 Mar 2004)

  07 Mar 2004; Robin H. Johnson <robbat2@gentoo.org> itcl-3.2.1-r1.ebuild:
  add prospective fix for bug #43770

*itcl-3.2.1 (28 Oct 2003)

  28 Oct 2003; Robin H. Johnson <robbat2@gentoo.org> itcl-3.2-r2.ebuild,
  itcl-3.2.1.ebuild, files/itcl-3.2.1-gentoo.diff:
  add error checking to old ebuild, and rewrite new ebuild for version bump

  26 Oct 2003; Brad House <brad_mssw@gentoo.org> itcl-3.2-r2.ebuild:
  add amd64 flag

  09 Sep 2003; Aron Griffis <agriffis@gentoo.org> itcl-3.2-r2.ebuild:
  Mark stable on alpha

  08 Jul 2003; Aron Griffis <agriffis@gentoo.org> itcl-3.2-r2.ebuild:
  Add ~alpha to KEYWORDS

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*itcl-3.2-r2 (27 May 2002)

  09 Aug 2002; George Shapovalov <george@gentoo.org> itcl-3.2-r2.ebuild :

  fixed build problems - removed "bad" parts of the patch

  27 May 2002; Seemant Kulleen <seemant@gentoo.org> itcl-3.2-r2.ebuild
  files/digest-itcl-3.2-r2 files/itcl-3.2-r2-gentoo.diff :

  Adjusted dependency to generic dev-lang/tk instead of specific tk version,
  and adjusted man page locations to be LFH compliant. This closes bug #2936
  by kodath@freezingmail.com

*itcl-3.2-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.