Log message:
Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.

Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
Updated to 0.74

Changes:

0.74 2012-01-25
- Documentation:
    * Re-release of 0.73, now with a proper changelog

0.73 2012-01-25
- Fixes:
    * Allow prefetching of only a subset of the other table's columns (Alex Vandiver)
    * Avoid a compilation failure on blead caused by incorrect precedence \ 
(Thomas Sibley)

Log message:
Update p5-Jifty-DBI to 0.72.

Changes from previous:
0.72 2011-10-17
- Fixes:
    * Handle DBH connection errors, retry the query (Luke Closs)

- Documentation:
    * Mention old_value in after_* hooks (Thomas Sibley)

0.71 2011-06-17
- Fixes:
    * Ensure canonicalization and validation triggers are properly found
      (Thomas Sibley)

0.70 2011-06-15
- Fixes:
    * Respect manual column sort_orders (Thomas Sibley)
    * Produce more useful error messages during schema upgrades (Thomas Sibley)

- Documentation:
    * Clarify what value after_set_* hooks receive (Thomas Sibley)

0.69 2011-05-17
- Fixes:
    * Remove some instances of qw() as parentheses deprecated in 5.14 (sunnavy)

Log message:
Revision bump after updating perl5 to 5.14.1.

Log message:
Update p5-Jifty-DBI to 0.68.

0.68 2011-04-14
- Security:
    * Prevent SQL injection in column names, operators, order and group by
      (Alex Vandiver)
    * Fix distinct_query to catch injection and correctly rewrite to
      function => '' (Alex Vandiver)
    * Prevent SQL injection via IS

- Fixes:
    * There is no need to check $args{column} around our LIKE adjustments
      (Alex Vandiver)
    * Slightly unify nigh-identical codepaths between Pg and Oracle
      (Alex Vandiver)

0.67 2011-02-28
- Features:
    * Make ->distinct_column_values use ->simple_query, thus going through our
      SQL logging infrastructure (Alex Vandiver)

- Fixes:
    * Set raw_values in load_by_hash so the __raw_value method works when the
      record is loaded by a collection (Thomas Sibley)

- Tests:
    * Author tests for no tabs (Shawn M Moore)

0.66 2011-02-14
- Features:
    * Provide a sane way to wrap a function around an aliased column in order_by
    * Pass old_value to triggers on column update

- Fixes:
    * Respect the 'by' attribute for refers_to columns in create and set
    * Use the right FK when using a record object in load_by_cols or
      limit [rt.cpan.org #64779]
    * Don't encode fields when attempting to limit with IS
    * Fix since/till by refactoring columns to use an updated all_columns

- Installation:
    * Only run these URI filter tests if we have URI [rt.cpan.org #65047]

0.64 Wed Dec  8 15:21:17 EST 2010
- Installation:
    * Minor distribution fixes

0.63 Wed Dec  8 15:14:17 EST 2010
- Features:
    * distinct_column_values method, docs and tests

- Fixes:
    * Warn about load(arg => value)
    * Include column_name in the value passed to reader warning
    * It is a rare but possible case that 0 is a valid id
    * Ensure encode_base64 doesn't choke on utf8

0.62 Thu May 20 13:58:53 EST 2010
- Features:
    * Computed columns let you have the Jifty-DBI scaffolding but without
      touching the database
    * Column->is_boolean

- Fixes:
    * Don't attempt to store undef values in memcached
    * Avoid undef warnings

0.61 Mon Jan  4 13:04:20 EST 2010
- Installation:
    * Minor distribution fixes

0.60 Mon Jan  4 13:02:17 EST 2010
- Features:
    * Allow passing of extra parameters to canonicalizers
    * Add an attribute which controls placeholder use for load_by_cols

- Fixes:
    * Don't add LOWER() on <= or >= operators, only = and !=
    * Better case sensitivity tests
    * Expose quote_value() on Jifty::DBI::Handle
    * When generating COUT, don't add a DISTINCT unless needed
    * Fix t/12prefetch.t's assumptions on row ordering

Log message:
Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.

sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!

Log message:
Update p5-Jifty-DBI from version 0.58 to version 0.59.

Upstream changes:
0.59 Wed Nov 18 20:12:57 EST 2009
- Features:
    * Support a special value of "all" in set_page_info

- Fixes:
    * Make "default is ''" propagate correctly to ALTER and CREATE TABLE
      statements

- Installation:
    * Our Module::Install was hilariously out of date

Log message:
Update p5-Jifty-DBI from version 0.53 to version 0.58.

Pkgsrc changes:
- Perl 5.10, which includes version.pm, is now required by pkgsrc, hence
the dependency on devel/p5-version can be removed
- Set LICENSE

Upstream changes:
0.58 Tue Jul 14 03:21:21 EST 2009
- Possible incompatibilities:
    * Modules which use Jifty::DBI::Schema will have strict and warnings
      automatically applied to them.

- Features:
    * Jifty::DBI::Handle now has methods for supported_drivers,
      available_drivers, and is_available_driver.

- Fixes:
    * Remove unused _limit_clause method
    * Various error message improvements
    * Use ->new_item instead of ->record_class->new since it was a \ 
performance
        hit in Jifty
    * Avoid cals to ->new_item where possible

- Documentation:
    * Document connect's quirky return value

0.57 Tue May 19 08:02:03 EDT 2009
- Major bugfixes:
    * Use eval {} in Jifty::DBI::Handle's DESTROY block when manipulating DBI
        Alterations to the DBI object in the DESTROY block must be wrapped in
        an eval {}, as object destruction order is not guaranteed during
        global destruction, and this interacts poorly with DBI's tie'd object.
    * During DESTROY, don't explicitly disconnect a dbh set InactiveDestroy
        The InactiveDestroy flag on DBI objects prevent them from being
        implicitly disconnected when they go out of scope -- for example, in
        the case where a process has forked, and two processes hold the socket
        open.
        However, it does not prevent them from being _explicitly_
        disconnected, as we were doing in Jifty::DBI::Handle's DESTROY method.
        This caused InactiveDestroy to never kick in, causing either a shared
        socket, or two closed handles after a fork.  We prevent this by having
        Jifty::DBI::Handle respect InactiveDestroy in its DESTROY method.
    * Do not use Scalar::Defer defaults for columns' defaults in the db

- New features:
    * Add a display_length attribute on columns
    * add schema manipulation tables: rename_column and rename_table
    * If a column's default is a record, call its id method

- Fixes:
    * Improve SQL error message and avoid its duplication
    * Pull the input_ and output_filters out of the instance hash

- Tests:
    * Added a unit test for the SaltHash filter
    * use drop_table_if_exists in tests
    * add drop_table_if_exists in t/utils.t
    * unconditionaly drop tables for testing
    * test rename_table
    * add tests for rename_column
    * SaltHash test does not need an is_deeply()
    * Don't explicitly disconnect the handle, DESTROY handles it better
    * Test for warnings instead of letting them leak into the test output