perl-embperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerald Richter" <>
Subject Re: DBIx::Recordset status
Date Wed, 08 Oct 2003 16:23:48 GMT

it's true DBIx::Recordset hasn't been updated for a long time. The reason is
simple, it does all I need :-) Anyway I have a set of patches people send me
and it would be worth putting them into a new release. Also there are some
ideas what can be enhanced. As you already know I don't have the time to do
it right now and when I have time I like to put it into Embperl to get 2.0
finaly done.

So maybe somebodyelse could help in maintaining DBIx::Recordset (or take
over the maintainance). I can setup a public CVS (or better svn) which holds
the sources, so it should be quite easy to cooperate.

I think the work Angus has already done for the Debian release is a good
starting point. Also the docs Terrence has written should be considered to
be included

Anybody likes to give it a try?


Angus Lees wrote:
> At Thu, 2 Oct 2003 17:41:36 -0700, Terrence Brannon wrote:
>> The Perl object-oriented Persistence group
>> (, has
>> stated that their list of reviewed modules will drop DBIx::Recordset
>> within
>> six months unless it appears that the module is being maintained
>> (ie, new
>> releases are made).
> <aside>
> I find it interesting that they only consider code worthwhile if its
> not finished yet..
> I really don't get this "newer is better" philosophy that is so
> prevalent in new-age computing circles.  From what I can see, "being
> new" is a point *against* the quality of a piece of code.
> </aside>
>> But they were wondering if a new release were coming out or if there
>> were
>> any outstanding bugfixes/features to be done to the code.
> I've accumulated quite a few bugfixes from various sources.  I
> seriously recommend anyone distributing DBIx::Recordset look over
> them, they should be trivial to separate from the Debian-specific
> packaging parts:
> The debian/changelog file (and<number> where a
> bug number is given) should give details about each patch where its
> purpose isn't already obvious.

Gerald Richter     ecos electronic communication services gmbh
IT-Securitylösungen * dynamische Webapplikationen * Consulting

Post:       Tulpenstrasse 5          D-55276 Dienheim b. Mainz
E-Mail:          Voice:   +49 6133 939-122
WWW:      Fax:     +49 6133 939-333
|   ECOS BB-5000 Firewall- und IT-Security Appliance:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message