Re: intent to package some perl/dbi/postgress stuff

[Craig Sanders <cas@taz.net.au>]

On 23 Sep 1998 mdorman-debian-devel@debian.org wrote:

> Craig Sanders <cas@taz.net.au> writes:
> > libdbi-perl        1.02   latest version of libdbi-perl, includes support
> >                           for dbd proxy. non-maintainer release. 
> >                           this one is really maintained by Ben Gertzfield
> >                           <che@debian.org>
> 
> Ben sort of officially ceded (in private email) libdbi-perl to me
> about a month ago, and I packaged up 1.00, but I've been trying to
> figure out how to resolve the problem that the interface changed,
> which requires all dbds to be recompiled. :-(

yeah, ben said that he had people who wanted it.

> If you want it, though, it's yours.

no thanks, i don't really have time. i'll do it if nobody else will, but
i'd rather not.



my solution to the "interface has changed" problem was to completely
ignore it. 

i had to recompile DBD::Pg.  

DBD::Xbase seems to still work without recompilation (looks like it is all
perl, no C code in it).

i don't use any other DBD modules, so i don't know whether they need
recompiling or not.


i don't think this will be a big problem, as long as it is co-ordinated
with all dbd packages. so far, that seems to be:

    libdbd-mysql-perl
    libdbd-msql-perl
    libxbase-perl        (this one doesn't appear to need recompilation)

and the two that i packaged are already compiled with libdbi-perl 1.02:

    libperl-dbd-pg
    libperl-dbd-pnet


so that means only two packages need to be recompiled so that we can have
a post-1.0 release version of libdbi-perl.  seems worth it to me.  mail a
copy of the new libdbi-perl to the mysql and msql dbd maintainers, and
release when they have recompiled their packages. 

craig

PS: we need a naming convention for dbd modules. i suggest "dbd-XXXX",
i.e. rename the above to "dbd-mysql", "dbd-msql", "dbd-pg", etc.
DBD implies perl, so the ".*lib.*perl.*" isn't redundant.

--
craig sanders