Ted Behling <[EMAIL PROTECTED]> wrote:
> Sorry for replying to my own e-mail, but I had another thought. What
> about just failing gracefully if SQLite2 isn't available? If it's
> installed, it gets used; if not, a warning is shown and the dependent
> tests are skipped.
That's what it does right now. The tests don't depend on SQLite2
per-se, just a DSN that points to a DBI driver that supports transactions
(eg; pretty much everything except MySQL ;-)
But then groups like ActiveState and Debian might end up packaging
this thing up (automatically or not) without ever running the unit tests
properly against their distributions, because "make test" passes by skipping
all the relevant tests. IMHO that's bad Quality Assurance on their part and
mine... so I'm striving for something better.
Another option that occured to me while I was loading the dishwasher
was bundling SQLite2 (or something like it) in my t/ directory. Sure, it
will consume a bit of extra bandwidth when the package is downloaded, but it
won't leave the bloat around once it's tested, installed (or packaged up
into something like a .deb or .ppd), and the source tree is purged. But I
still find myself thinking "there's got to be a better way"...
- Tyler
