audio/amarok-kde3: extract with gtar

There's something amiss with the amarok tarball, bsdtar won't fully
extract it.  The file '._gem_commands.rb' will be missing unless GNU Tar
is used instead.  Other platforms, like ArchLinux, have run into this
as well.  The solution is mandate gtar for the file extraction.
Update to 0.53: needed for davical-1.1.1.
New file Multipart.php.
Updated devel/php-libawl to 0.53
Update to 1.1.1:

1.1.1:
There are no database changes in this release

Bug Fixes

    Unassigned variable warning in Principal.php calling BuildDeadPropertyXML
    Notification of deletes when hide_older_than is set
    Fixes to URL encoding of some CalDAV/CardDAV properties
    Fix to Basic Auth handling in admin UI
    Fix CalDAV client library to handle multiple 'Allow' headers in OPTIONS response
    Fix ldap driver to handle numeric usernames correctly.
    Add handling for allprop and ommission of prop tag in calendar-query, calendar-multiget and addressbook-query
    Fix parsing of relative alarm times where the event has a timezone
    Correct detection of suhosin.server_strip status (from Christoph Anton Mitterer via debian bug #656392).
    Other minor bugfixes.

Other Changes

    Add support for ldap mapping of multiple fields to one DAViCal field (from Sylvain BURGER)
    Generally improved support for a wider range of DAV/CalDAV/CardDAV properties in calendar-query, calendar-multiget and addressbook-query

1.1.0:
Database Upgrade

There are several changes to in-database functions.

Bug Fixes

    Obscure password in LDAP debug log messages
    Fix bugs parsing some RFC5545 duration values
    Fix handling of ?mode=append when uploading calendar data.
    Various fixes to external BIND support.
    Fix some errors in content-type detection & handling.
    Correct round-trip handling of arbitrary XML in dead properties.
    Fix bugs in editing of existing grants.

Other Changes

    Support for WebDAV Synchronisation is updated to match the final RFC.
    Support If-Modified-Since header.
    Merge iSchedule support from Rob Ostenson.
    Add support for initialising an addressbook from a file of VCARDs
    Add support for 'Prefer' and 'Brief' headers.
    Reduce logging noise from 401 and 404 responses.
    Some query performance improvements.
    When someone is delegated 'write' by a principal they can now maintain that principal's details in the Admin UI.
    New default_collections setting which replaces home_calendar_name and home_addressbook_name (these are deprecated)
Updated www/davical to 1.1.1
Update to 1.12.3:

New in 1.12.3:

* WARNING: Future backward-incompatibilities!

  - Future versions of Automake will likely drop support for the
    long-deprecated 'configure.in' name for the Autoconf input file.
    You are advised to use the recommended name 'configure.ac' instead.

  - The long-obsolete (since automake 1.10) AM_PROG_MKDIR m4 macro will
    be removed in Automake 1.13.  The $(mkdir_p) make variable and the
    @mkdir_p@ substitution will still remain available (as aliases of
    $(MKDIR_P)) for the moment, for better backward compatibility.

  - Autoconf 2.65 or later will be required by the next major Automake
    version (1.13).  Until now, Automake has required Autoconf version
    2.62 or later.

  - Starting from the next major Automake version (1.13), the rules
    to build pdf, ps and dvi output from Texinfo input will use the
    '--build-dir' option by default.  Since such an option was only
    introduced in Texinfo 4.9, this means that Makefiles generated by
    future Automake versions will require at least that version of
    Texinfo.

  - Starting from the next major Automake version (1.13), the parallel
    testsuite harness (previously only enabled by the 'parallel-tests'
    option) will become the default one; the older serial testsuite
    harness will still be available through the use of the 'serial-tests'
    option.

  - The following long-obsolete m4 macros will be removed in the
    next major Automake version (1.13):

      AM_PROG_CC_STDC:    superseded by AC_PROG_CC since October 2002
      fp_PROG_CC_STDC:    broken alias for AM_PROG_CC_STDC
      fp_WITH_DMALLOC:    old alias for AM_WITH_DMALLOC
      AM_CONFIG_HEADER:   superseded by AC_CONFIG_HEADERS since July 2002
      ud_PATH_LISPDIR:    old alias for AM_PATH_LISPDIR
      jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
      ud_GNU_GETTEXT:     old alias for AM_GNU_GETTEXT
      gm_PROG_LIBTOOL:    old alias for AC_PROG_LIBTOOL
      fp_C_PROTOTYPES:    old alias for AM_C_PROTOTYPES (which was part
                          of the now-removed automatic de-ANSI-fication
                          support of Automake)

  - All the "old alias" macros in 'm4/obsolete.m4' will be removed in
    the next major Automake version (1.13).

  - Support for the two- and three-arguments invocation forms of the
    AM_INIT_AUTOMAKE macro is deprecated, and will be removed in the
    next major Automake version (1.13).

  - The '--acdir' option of aclocal is deprecated, and will probably
    be removed in the next major Automake release (1.13).  You should
    use the options '--automake-acdir' and '--system-acdir' instead
    (which have been introduced in Automake 1.11.2).

  - The exact order in which the directories in the aclocal macro
    search path are looked up is probably going to be changed in the
    next Automake release (1.13).

  - The 'missing' script will not try anymore to update the timestamp
    of out-of-date files that require a maintainer-specific tool to be
    remade, in case the user lacks such a tool (or has a too-old version
    of it).  In fact, starting from Automake 1.13, all it'll do will be
    giving more useful warnings than a bare "command not found" from a
    make recipe would.

* Miscellaneous changes:

  - The '.m4' files provided by Automake does not define serial numbers
    anymore.  This should cause no difference in the behaviour of aclocal
    though.

  - Some testsuite weaknesses and spurious failures have been fixed.

  - There is initial support for automatic dependency tracking with the
    Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.

Bugs fixed in 1.12.3:

* Long-standing bugs:

  - Instead of renaming only self-references of files (typically for
    #lines), ylwrap now also renames references to the other generated
    files.  This fixes support for GLR and C++ parsers from Bison (PR
    automake/491 and automake bug#7648): 'parser.c' now properly
    #includes 'parser.h' instead of 'y.tab.h'.

  - Generated files unknown to ylwrap are now preserved.  This fixes
    C++ support for Bison (automake bug#7648): location.hh and the
    like are no longer discarded.
Updated devel/automake to 1.12.3
Update to 20120607. The usual fixes.
Updated textproc/ispell-german to 20120607
+ openmsx-0.9.0.
Initial addition of shtk 1.0.

Despite its pretentious name, this package is just an attempt to generalize
a bunch of code that I keep reusing every time I implement shell scripts.
In particular, this is about to remove tons of duplicate stuff from both
sysbuild and sysupgrade in subsequent commits and I'll probably use it again
for some other stuff I have in mind.

Description follows:

The Shell Toolkit, or shtk for short, is a collection of modules written in
sh(1) that provide common functionality to simplify the implementation of
complex shell scripts.  These modules provide things like utilities to
manipulate data types, helpers to expose a common CLI, or higher-level
abstractions such as the processing of configuration files.

The included shtk(1) utility exposes convenience functionality to let the
user "build" shell scripts that use shtk.  Build, in this case, just means
adding common boilerplate code to the initialization of the script to load
the shtk common code.
Add and enable shtk.
Update to 2.1:

- Use shtk for the common utilities and configuration file parsing
  functionality.  The local copies of the "config" and "utils" modules
  are gone.
Update to 1.1:

- Use shtk for the common utilities and configuration file parsing
  functionality.  The local copies of the "config" and "utils" modules
  are gone.
Note addition of shtk 1.0 and upgrades of sysbuild to 2.1 and
sysupgrade to 1.1 (both of which now use shtk).