# ChangeLog for media-sound/mp3blaster # Copyright 2002-2005 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/media-sound/mp3blaster/ChangeLog,v 1.20 2005/04/08 17:27:25 hansmi Exp $ 08 Apr 2005; Michael Hanselmann mp3blaster-3.2.0.ebuild: Stable on ppc. 29 Dec 2004; Ciaran McCreesh : Change encoding to UTF-8 for GLEP 31 compliance 22 Nov 2004; Markus Rothe mp3blaster-3.2.0.ebuild: Added ~ppc64 to KEYWORDS; bug #72100 30 Oct 2004; Jeremy Huddleston -mp3blaster-3.1.1.ebuild: toolchain love for bug #69012. 13 Jul 2004; Bryan Østergaard mp3blaster-3.2.0.ebuild: Stable on alpha. 23 Jun 2004; Jeremy Huddleston mp3blaster-3.2.0.ebuild: Stable amd64 and sparc. Added USE=lirc support. 07 Jun 2004; Aron Griffis mp3blaster-3.1.3.ebuild, mp3blaster-3.2.0.ebuild: Fix use invocation 31 Mar 2004; Jeremy Huddleston mp3blaster-3.2.0.ebuild: Stable on x86. *mp3blaster-3.2.0 (28 Nov 2003) 28 Nov 2003; Greg Fitzgerald mp3blaster-3.2.0.ebuild: Version bump. 16 Nov 2003; Brad House mp3blaster-3.1.3.ebuild: mark stable on amd64 12 May 2003; Jason Wever mp3blaster-3.1.1.ebuild, mp3blaster-3.1.3.ebuild: Added ~sparc to keywords. *mp3blaster-3.1.3 (05 Nov 2002) 15 Dec 2002; Bjoern Brauel mp3blaster-3.1.3.ebuild : Add ~alpha to KEYWORDS 08 Nov 2002; Daniel Ahlberg mp3blaster-3.1.3.ebuild : Updated SRC_URI. 05 Nov 2002; Daniel Ahlberg : Version bump. *mp3blaster-3.1.1 (13 Aug 2002) 15 Dec 2002; Bjoern Brauel mp3blaster-3.1.1.ebuild : Add alpha to KEYWORDS 13 Aug 2002; Arcady Genkin mp3blaster-3.1.1.ebuild : Updated the ebuild for 3.1.1 to exclude support for NAS, as it appears to be broken (see bug 5183). *mp3blaster-3.1 (10 Jun 2002) 10 Jun 2002; Ryan Phillips mp3blaster-3.1.ebuild : New versionn *mp3blaster-3.0_p8 (28 Mar 2002) 28 Mar 2002; Seemant Kulleen mp3blaster-3.0_p8.ebuild : the vorbis USE flag is now called oggvorbis *mp3blaster-3.0_p8 (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.