[DBD-SQLite] Using System SQLite Instead of Bundled Version

Adam Kennedy adamkennedybackup at gmail.com
Mon May 25 07:35:42 GMT 2009

As I noted before, there's a good reason I just zero'ed the code out.

If you guys want to apply a local patch to false -> true that block,
I'm ok with that. Debian are hardly the worst offenders when it comes
to patches and linking things in.

To enable it again more generally, I'd like to see some more strict
tests that do similar things to DBIx::Class, tests that the embedded
version will always pass, but that validate the the system-linked
version is "good enough" for us to use.

A lack of strictness in validating the system SQLite was what
previously caused us problems.

If we can add the quality of validation we need to "protect" the
module, then we can re-enable it by default again.

Adam K

2009/5/22 Jonathan Yu <jonathan.i.yu at gmail.com>:
> Hi:
> On Fri, May 22, 2009 at 6:20 AM, Kenichi Ishigaki <kishigaki at gmail.com> wrote:
> I agree with you here. However, what I was asking for is simply to
> re-enable the behaviour before, where a variable/parameter to
> Makefile.PL gets to decide which to do. Definitely, other systems may
> not have an up-to-date system sqlite installation and cannot be
> guaranteed thus, so I do think that your argument to remove that
> functionality is valid. On the other hand, I don't see the harm in
> defaulting to the embedded version but also allowing people to choose
> to use the system-installed version if they wish, hopefully knowing
> the risks of doing so.

More information about the DBD-SQLite mailing list