- Adds textproc/p5-XML-SAX-Writer as a RUN_DEPENDS
- Removes the pkgspec from the RUN_DEPENDS because all of the required
versions are lower than the oldest version in the tree
ok simon@, steven@
Manager version H3 (2.1.2).
This is a bugfix release that also fixes privilege escalation in the Horde API
and missing ownership validation in the share management. All users are
encouraged to upgrade to this version.
The major changes compared to the Mnemo H3 (2.1.1) version are:
* Fixed privilege escalation in the Horde API.
* Fixed missing ownership validation on share changes.
* Updated Finnish, Japanese, Portuguese, Simplified Chinese, Spanish, and
Traditional Chinese translations.
* Small bug fixes and improvements.
The full list of changes (from version H3 (2.1.1)) can be viewed here:
http://cvs.horde.org/diff.php/mnemo/docs/CHANGES?r1=1.63.2.37&r2=1.63.2.38.2.3&ty=h
Storm is a fast object-relational mapper (ORM) for Python and used in
Canonical's Launchpad project. Storm is developed in a test-driven
manner, provides small and clean public APIs and works with everything
from SQLite to PostgreSQL and MySQL.
From Will Maier
ok kili@, eric@
DBIx::DataModel is a wrapper framework for building Perl abstractions
(classes, objects and datastructures) that interact with relational
database management systems (RDBMS). Of course the ubiquitous DBI
module is used as a basic layer for communicating with databases; on
top of that, DBIx::DataModel provides facilities for generating SQL
queries, joining tables automatically, navigating through the results,
converting values, and building complex datastructures so that other
modules can conveniently exploit the data.
ok sthen@
Testing with databases can be tricky. If you are developing a system
married to a single database then you can make some assumptions about
your environment and ask the user to provide relevant connection
information. But if you need to test a framework that uses DBI,
particularly a framework that uses different types of persistence
schemes, then it may be more useful to simply verify what the framework
is trying to do -- ensure the right SQL is generated and that the
correct parameters are bound.
DBD::Mock makes it easy to just modify your configuration (presumably
held outside your code) and just use it instead of DBD::Foo (like
DBD::Pg or DBD::mysql) in your framework.
ok sthen@
- enable linking against already installed libdb.so instead of the
internally shipped static library
"no objections here" martynas@
mostly done somewhere between budapest and amsterdam
