# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
# $Header: /var/cvsroot/gentoo-x86/dev-perl/SDL-sdlpl/ChangeLog,v 1.6 2002/06/05 13:40:13 seemant Exp $

*SDL-sdlpl-1.18.4 (5 Jun 2002)

  5 Jun 2002; Seemant Kulleen <seemant@gentoo.org> SDL-sdlpl-1.18.4.ebuild
  files/digest-SDL-sdlpl-1.18.4 :

  Dave Goehrig of sdlperl.org has kindly issued this release to help us sort
  the silly Mesa headers thing.  It turns out, however, that we need to
  supply sdl-perl's compilation process the headers to nvidia's gl.h and
  glu.h files.

*SDL-sdlpl-1.18.3 (4 Jun 2002)

  4 Jun 2002; Seemant Kulleen <seemant@gentoo.org> SDL-sdlpl-1.18.3.ebuild
  files/digest-SDL-sdlpl-1.18.3 :

  Version bump which is patched to work against the SDL headers.  Mesa is
  still an undecided issue at this point.  Thanks to David J. Goehrig of
  sdl-perl.org for putting out a patch so quick.

*SDL-sdlpl-1.18.2 (4 Jun 2002)

  4 Jun 2002; Seemant Kulleen <seemant@gentoo.org> SDL-sdlpl-1.18.2.ebuild
  files/digest-SDL-sdlpl-1.18.2 :

  Version bump.

*SDL-sdlpl-1.18 (30 May 2002)

  30 May 2002; Seemant Kulleen <seemant@gentoo.orG> SDL-sdlpl-1.18.ebuild
  files/digest-SDL-sdlpl-1.18 :

  Version bump thanks to: subdcc@501.xor.pl (Pawel SUchanecki) in bug#3227

*SDL-sdlpl-1.17 (20 May 2002)

  20 May 2002; Seemant Kulleen <seemant@gentoo.org> SDL-sdlpl-1.17.ebuild
  files/digest-SDL-sdlpl-1.17 :

  Version bump.

  25 Feb 2002; Leo Lipelis <aeoo@gentoo.org> files/digest-SDL-sdlpl-1.12,
  SDL-sdlpl-1.12.ebuild:

  Initial ebuild.

*SDL-sdlpl-1.12 (25 Feb 2002)

  1 Feb 2002; G.Bevin <gbevin@gentoo.org> skel.ChangeLog :
  
  This changelog is targetted to users. This means that the comments should be
  well explained and written in clean English. 
  
  Every new version or revision of the package has to be marked by a '*'
  seperator line as above. Changements since the last revision have to be
  added to the top of the file, underneath the initial copyright and cvs header
  comments, in exactly the same format as this comment.
  
  This means that you start with header line that has the following format :
  
      date; your_name <your_email> changed_file1, changed_file2 :
	  
  Below that line your explanation should follow. It has to be indented,
  paragraphed and wrapped at a linewidth of 80 characters.
  
  Any details about what exactly changed in the code should be added as a
  message when the changes are committed to cvs, not in this file.