On Mon, Jun 16, 2003 at 02:27:31AM -0400, Rudy Lippan wrote:
> On Wed, 11 Jun 2003, Tim Bunce wrote:
> 
> > Date: Wed, 11 Jun 2003 12:23:54 +0100
> > > DBD::mysql is packaged as a bundle. When I do a release, will I also need 
> > > to bump the version number on the bundle?
> > 
> > Yes, but the Makefile.PL says
> > 
> >     'VERSION_FROM' => 'lib/DBD/mysql.pm'
> > 
> > so it'll be looked after for you :)
> 
> On cpan there are two "Bundle::DBD::mysql's" one is version 2.0419 and one 
> is 2.0416.

Umm, http://search.cpan.org/search?query=bundle%3A%3ADBD%3A%3Amysql&mode=all
lists two when searching for "all":

        Bundle::DBD::mysql
        A bundle to install Perl drivers for mSQL or MySQL
        Msql-Mysql-modules-1.2219 - 30 Oct 2001 - Jochen Wiedmann

        Bundle::DBD::mysql
        A bundle to install Perl drivers for mSQL or MySQL
        DBD-mysql-2.1027 - 31 May 2003 - Jochen Wiedmann

but only one when searching for "modules". Odd.


> 2.0419 has Msql-Mysql-modules-1.2219 and 2.0416 has  
> DBD-mysql-2.1027 and 1.2219 is not in the Changelog.  So I am a lttile 
> confused as to why the current version has a Bundle version that is < the 
> previous version?

Personally I think using four digits for subversion is over the top.
I'd suggest you not worry too much about past confusions and bump
the version on everything to 2.9001 for now.

Once the prepared statement code gets integrated then go to a nice
simple 3.00 :)

> > p.s. I'd like to see mysql.pod merged into mysql.pm. Just add it after a
> > __END__ token then perl won't even bother reading it when it loads the driver.
> 
> Done.

Thanks.

Tim.

Reply via email to