Log message:
Fix compatiblity with png 1.5 by taking png.c from newest snapshot.
OCVS: ----------------------------------------------------------------------

Log message:
png shlib name changed for png>=1.5.0, so bump PKGREVISIONs.

Log message:
Mechanically replace references to graphics/jpeg with the suitable
alternative from mk/jpeg.buildlink3.mk

This allows selection of an alternative jpeg library (namely the x86 MMX,
SSE, SSE2 accelerated libjpeg-turbo) via JPEG_DEFAULT=libjpeg-turbo, and
follows the current standard model for alternatives (fam, motif, fuse etc).

The mechanical edits were applied via the following script:

#!/bin/sh
for d in */*; do
  [ -d "$d" ] || continue
  for i in "$d/"Makefile* "$d/"*.mk; do
    case "$i" in *.orig|*"*"*) continue;; esac
    out="$d/x"
    sed -e 's;graphics/jpeg/buildlink3\.mk;mk/jpeg.buildlink3.mk;g' \
        -e 's;BUILDLINK_PREFIX\.jpeg;JPEGBASE;g' \
        < "$i" > "$out"
    if cmp -s "$i" "$out"; then
      rm -f "$out"
    else
      echo "Edited $i"
      mv -f "$i" "$i.orig" && mv "$out" \ 
"$i"
    fi
  done
done

Log message:
Bump PKGREVISION for libpng shlib name change.
Also add some patches to remove use of deprecated symbols and fix other
problems when looking for or compiling against libpng-1.4.x.

Log message:
* enable jbig support, add dependency to jbigkit.
* ghostscript-font-std part had been moved from ghostscript-fonts to
  urw-fonts.  add dependency on urw-fonts and adjust gs-font-dir.

Bump PKGREVISION (and ABI bump).

Log message:
Fix included path to ghostscript fonts by giving explicit path.
From obache@

Log message:
Note for LICENSE.

Log message:
Update GraphicsMagick to 1.3.12.

1.3.12 (March 8, 2010)
==========================

Security Fixes:

  * Updated libpng Windows sources to 1.2.43 in order to resolve
    CVE-2010-0205 as it pertains to the GraphicsMagick Windows build.

Bug fixes:

  * Filter mode (write to stdout) was completely broken.

  * Should now compile with libpng 1.4.

  * Windows PerlMagick build identified itself as the wrong version.

New Features:

  * None

Feature improvements:

  * None

Performance Improvements:

  * None

Behavior Changes:

  * DCX output format is only written on request.  Previously the PCX
    coder would automatically switch to DCX format if multiple frames
    would be written.

Log message:
Update GraphicsMagick to 1.3.11.

1.3.11 (February 21, 2010)
==========================

Security Fixes:

  * Fixed array underflow on systems using signed char which could
    result in a program crash due to extended characters in filenames
    or in certain file formats.

Bug fixes:

  * Fixed array underflow on systems using signed char which could
    result in a program crash due to extended characters in filenames
    or in certain file formats.

New Features:

  * Added a -thumbnail command to 'convert' and 'mogrify'.  This is a
    faster way to scale down the image when speed is a primary
    concern.

  * Added a -extent command to 'convert' and 'mogrify' which
    composites the image on top of a backing canvas image of solid
    color.

  * Added support for -compose to the 'convert' and 'mogrify', which
    were documented to support it (but did not).

Feature improvements:

  * None

Performance Improvements:

  * Requests for 'Over' and 'Atop' composition are converted to a
    request for the (faster) 'Copy' composition when both images are
    opaque.

Behavior Changes:

  * None

Log message:
Update GraphicsMagick to 1.3.10.

1.3.10 (February 10, 2010)
==========================

Security Fixes:

  * None

Bug fixes:

  * +adjoin was not working correctly for the case when only one image
    frame is present.  With +adjoin and writing one frame to
    "foo%d.jpg" it was outputting "foo%d.jpg" rather than \ 
"foo0.jpg".

  * When drawing paths, memory allocation for the points was much
    larger than it needed to be (patch by Vladimir Lukianov).

New Features:

  * None

Feature improvements:

  * None

Performance Improvements:

  * None

Behavior Changes:

  * To reiterate the change which first appeared in 1.3.9, there is no
    longer an implicit +adjoin if the output file name happens to
    contain a %d sequence, or there are multiple frames and the output
    file format only supports storing one frame.  Specify +adjoin if
    scene number substition is desired in the output file names.