Log message:
Recursive PKGREVISION bump for libxml2 buildlink addition.

Log message:
Primary object is to make this build with libdvdread 4.2.0 (patch-ad)
Additionally:
 * Mark it as also working with libdvdread 4.1.3
 * Add comments to the patches
 * Add LICENSE=gnu-gpl-v2
This fixes all pkglint warnings.
OK'ed by wiz@

Log message:
recursive bump from gettext-lib shlib bump.

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:
Second try at jpeg-8 recursive PKGREVISION bump.

Log message:
Use the right option.

Log message:
bump revision because of graphics/jpeg update

Log message:
Remove @dirrm entries from PLISTs

Log message:
Don't force PentiumPro instructions to be used for GCC 4, just schedule
for it as the code originally intended.

Log message:
Simply and speed up buildlink3.mk files and processing.
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.