# ChangeLog for dev-python/pygtk # Copyright 2002-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/dev-python/pygtk/ChangeLog,v 1.18 2003/06/12 20:38:47 msterret Exp $ 12 Jun 2003; pygtk-1.99.13-r1.ebuild, pygtk-1.99.16.ebuild: fix Header *pygtk-1.99.16 (31 Mar 2003) 31 Mar 2003; foser pygtk-1.99.16.ebuild : New version *pygtk-1.99.15 (09 Feb 2003) 09 Feb 2003; foser pygtk-1.99.15.ebuild : New version *pygtk-0.6.11 (06 Dec 2002) 06 Dec 2002; Rodney Rees : changed sparc ~sparc keywords 06 Dec 2002; foser pygtk-0.6.11.ebuild : New version *pygtk-1.99.13-r1 (01 Nov 2002) 13 Nov 2002; Mark Guertin pygtk-1.99.13-r1.ebuild : backed down to ~ppc. Don't want dev builds of this sort which are not backwards compatible overwriting the proper relase. 01 Nov 2002; foser pygtk-1.99.13-r1.ebuild : Enabled threads support *pygtk-1.99.13 (23 Oct 2002) 24 Oct 2002; foser pygtk-1.99.13.ebuild : removed the author line, it made emerge ignore the ebuild 23 Oct 2002; Spider pygtk-1.99.13.ebuild : finally got this in, closing bug #3700. thanks foser@gentoo.org for the actual work *pygtk-0.6.9 (19 Jun 2002) 29 Jul 2002; George Shapovalov pygtk-0.6.8-r1.ebuild, pygtk-0.6.8-r2.ebuild, pygtk-0.6.9.ebuild, pygtk-1.99.9.ebuild, pygtk-1.99.10.ebuild : Added KEYWORDS,SLOT,LICENSE (where missing), header clean-ups 19 Jun 2002; Gabriele Giorgetti pygtk-0.6.9.ebuild New version, updated dependencies. Close bug #3891 *pygtk-1.99.10 (13 Jun 2002) 21 Aug 2002; Mark Guertin pygtk-1.99.10.ebuild : Added ppc to keywords 13 Jun 2002; Spider pygtk-1.99.10.ebuild : I've got a headache so this is a simple bump to the next level. and remember kids dont play in the playgrounds. *pygtk-1.99.9 (24 Apr 2002) 24 Apr 2002; Spider pygtk-1.99.9.ebuild pygtk-0.6.8-r2.ebuild Add SLOT update to gtk2 *pygtk-0.6.8-r1 (1 Feb 2002) 1 Feb 2002; G.Bevin 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.