# ChangeLog for gnustep-base/gnustep-env # Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/gnustep-base/gnustep-env/ChangeLog,v 1.12 2004/12/13 23:08:33 fafhrd Exp $ 13 Dec 2004; Armando Di Cianno gnustep-env-0.1.5.ebuild, -gnustep-env-0.1.ebuild: Cleaned up detection of objc and libff; general cleanups 23 Nov 2004; Jeremy Huddleston gnustep-env-0.1.5.ebuild: Stable amd64... bug #68857. *gnustep-env-0.1.5 (11 Nov 2004) 11 Nov 2004; Armando Di Cianno +files/gnustep.env-0.1.5, +files/gnustep.runscript-0.1.5, gnustep-env-0.1.4.ebuild, +gnustep-env-0.1.5.ebuild: Mass Update: gnustep.eclass revamped to allow configurable root install; gnustep-base/libs/apps updated to utilize new gnustep.eclass (only versions bumped where files would change); some KEYWORDS were accidentally dropped between version bumps of packages -- this has been resolved; windowmaker correctly supports gnustep now 31 Oct 2004; Jason Wever gnustep-env-0.1.4.ebuild: Added ~sparc keyword. 31 Oct 2004; Bryan Østergaard gnustep-env-0.1.4.ebuild: ~alpha keyword. 10 Oct 2004; David Holm gnustep-env-0.1.4.ebuild: Added to ~ppc. *gnustep-env-0.1.4 (03 Oct 2004) 03 Oct 2004; Armando Di Cianno files/gnustep.env-0.1.4, files/gnustep.runscript-0.1.4, gnustep-env-0.1.4.ebuild: Updated to use GENTOO_GNUSTEP_ROOT variable from gnustep.eclass 25 Jul 2004; Lina Pezzella : Fixed Manifest. *gnustep-env-0.1 (23 Jul 2004) 23 Jul 2004; Armando Di Cianno +files/10gnustep, +gnustep-env-0.1.ebuild: Moved from x11-wm/gnustep-env to gnustep-base/gnustep-env. 07 Jul 2004; Hardave Riar gnustep-env-0.1.ebuild: Stable on mips 19 Jun 2004; gnustep-env-0.1.ebuild: Added IUSE. 18 Feb 2004; David Holm gnustep-env-0.1.ebuild: Added to ~ppc. 12 Jun 2003; gnustep-env-0.1.ebuild: add Header 06 Dec 2002; Rodney Rees : changed sparc ~sparc keywords *gnustep-env-0.1 (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.