Log Message:
Updating databases/p5-ORLite from 0.31 to 0.40

pkgsrc changes:
- Adjust dependenies

Upstream changes:
1.40 Mon  1 Fed 2010
	- Fixed backwards test skipping logic

1.39 Fri 29 Jan 2010
	- Typo in the tests, they now run >= instead of > 1.05

1.38 Thu 28 Jan 2010
	- When using array => 1 on classes that we can create, add a ->set
	  method for setting parameters in the object safely.

1.37 Thu 28 Jan 2010
	- Adding experimental support for the array => 1 option.

1.36 Wed 27 Jan 2010
	- Rolled back the Template::Tiny conversion as it ended up slowing
	  down the code generation too much. I shall struggle on under the
	  old method.

1.35 Wed 27 Jan 2010
	- Adding experimental support for accelerated XS accessors
	  using Class::XSAccessor. ORLite itself will not introduce a
	  dependency on this module, consumers of this feature will need
	  to do it themselves.

1.34 Tue 26 Jan 2010
	- Major Change: Moved code generation from raw string appending to
	  using Template::Tiny instead. This will enable some new and more
	  complex improvements to the generated code.
	- Added tests for the cleanup code.

1.33 Sun 24 Jan 2010
	- When in the Perl debugger and on Perl 5.8.9 or newer,
	  use the $^P | 0800 in preference to dval (and always
	  use it even when $DEBUG is off).

1.32 Fri 15 Jan 2010
	- Each generated class now cleans up its own persistant
	  connection, rather than allowing it to fall through to the
	  deeper DBI cleanup.
	- To allow for persistant connections to readonly database,
	  we now always built transaction support for all databases.
	  However, for readonly databases we do not build the commit
	  method and you may only use the rollback method to end them.
	- Significantly expanded the Pod documentation to provide
	  documentation on all of the import options.
	- Add support for a cleanup option to import, which is single
	  explicit statement to be called on the database when the
	  process is shutting down. This should typically be used
	  ensure that a SQLite database is VACUUM'ed regularly (and at
	  a time when it hopefully won't impact the user much).