On Fri, Jun 19, 2009 at 01:16:20PM -0600, Curtis Jewell wrote: > On Fri, 19 Jun 2009 13:26 -0500, "David Dooling" > <[email protected]> wrote: > > > > Two possible solutions I can think of: > > > > > > > > 1) configure_requires. Doesn't help with old clients > > > > > > No, but it's the easiest way to help new ones. It can't hurt. > > > > This seems more applicable to DBD::SQLite than something that needs > > DBD::SQLite. Using that would require porting the entire DBD::SQLite > > build system to Module::Install (it currently uses > > ExtUtils::MakeMaker). > > Yes, it does, and no, it wouldn't require switching to M::I, because the > capability is already in there! > > DBD::SQLite's Makefile.PL includes this: > > OPTIONAL( '6.46', > META_MERGE => { > configure_requires => { > 'ExtUtils::MakeMaker' => '6.48', > 'File::Spec' => '0.82', # This is not > allowed to be computed > 'DBI' => $DBI_required, > }, ... > > so that if you have a client new enough to pick the configure_requires > line out of the META.yml, the problem should not arise in the first > place.
That would be great if DBD::SQLite could be made to do the right thing here. -- David Dooling http://www.politigenomics.com/ _______________________________________________ DBD-SQLite mailing list [email protected] http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite
