Hi Merijn, 'cause I don't have IRC at $work, we better discuss it on ML (when I'm able to answer in IRC, you're usually not online anymore (or not yet, respectively)).
<Tux> [Sno], SQL::Statement should not mention DBD::CSV in it's requirements <Tux> it now causes an endless loop <Tux> if DBD::CSV is installed (old) and SQL::Statement is installed (old) <Tux> whatever you do, cpan will get into trouble, as SQL::Statement requires DBD::CSV and DBD::CSV cannot pass tests because it depends on a recent SQL::Statement <Tux> so you will have to <Tux> 1. Hide the actual dependancy to DBD::CSV <Tux> 2. Guard your test code against $DBD::CSV::VERSION if you can load it <Tux> I now had to manually force install SQL::Statement before I could have cpan update DBD::CSV You have commit access to the SQL::Statement repository, feel free to apply the changes you mean, I review them and upload a new version afterwards. Probably it's time to prove whether DBD::CSV really requires SQL::Statement or couldn't run most business cases using DBI::SQL::Nano. Best regards, Jens
