Re: [DBD-SQLite] DBD-SQLite-Amalgamation-3.6.16
Ah, I must have used a wrong word (include). See http://search.cpan.org/~audreyt/DBD-SQLite-Amalgamation-3.6.16/ She doesn't need to do this. Kenichi On Thu, 30 Jul 2009 16:41:23 +1000, Adam Kennedy adamkennedybac...@gmail.com wrote: She needs to include it. The entire point is that you install DBD::SQLite::Amalgamation and it overwrites DBD::SQLite, but none of your code that uses SQLite needs to change. That's what it's there for. Adam K 2009/7/30 Kenichi Ishigaki kishig...@gmail.com: DBD::SQLite::Amalgamation 3.6.16 (the one Audrey released yesterday) is unauthorized release, which actually is nothing but repackaged DBD::SQLite 1.26_02 with original ::Amalgamation Changes. It won't be counted, so we don't need to care. That said, we might want to convince her not to include DBD::SQLite itself, but just to depend on it as DBD::SQLite is stable enough now (though we are still trying to make it better). Kenichi On Thu, 30 Jul 2009 14:23:53 +1000, Adam Kennedy adamkennedybac...@gmail.com wrote: Unless we see a release of SQLite that recommended updating, or reach a complete resolution to the various refactoring stuff that's being committed into the repository, or someone hits a critical bug, I consider the current release to be both stable and worth letting sit for a while, so there's time for all of downstream to converge. The release of DBD::SQLite::Amalgamation (for me) doesn't add any weight to the need to update. Adam K 2009/7/30 Darren Duncan dar...@darrenduncan.net: I noticed that Audrey released another DBD-SQLite-Amalgamation, after a year of not, that is said to be equivalent to the latest official dev release, citing that it would be redundant once the official release is no longer dev. Considering this, is it reasonable to push an official stable release of some kind now that has 3.6.16, or is it better to continue to wait on that front? -- Darren Duncan ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite
Re: [DBD-SQLite] DBD-SQLite-Amalgamation-3.6.16
Unless we see a release of SQLite that recommended updating, or reach a complete resolution to the various refactoring stuff that's being committed into the repository, or someone hits a critical bug, I consider the current release to be both stable and worth letting sit for a while, so there's time for all of downstream to converge. The release of DBD::SQLite::Amalgamation (for me) doesn't add any weight to the need to update. Adam K 2009/7/30 Darren Duncan dar...@darrenduncan.net: I noticed that Audrey released another DBD-SQLite-Amalgamation, after a year of not, that is said to be equivalent to the latest official dev release, citing that it would be redundant once the official release is no longer dev. Considering this, is it reasonable to push an official stable release of some kind now that has 3.6.16, or is it better to continue to wait on that front? -- Darren Duncan ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite
Re: [DBD-SQLite] DBD-SQLite-Amalgamation-3.6.16
DBD::SQLite::Amalgamation 3.6.16 (the one Audrey released yesterday) is unauthorized release, which actually is nothing but repackaged DBD::SQLite 1.26_02 with original ::Amalgamation Changes. It won't be counted, so we don't need to care. That said, we might want to convince her not to include DBD::SQLite itself, but just to depend on it as DBD::SQLite is stable enough now (though we are still trying to make it better). Kenichi On Thu, 30 Jul 2009 14:23:53 +1000, Adam Kennedy adamkennedybac...@gmail.com wrote: Unless we see a release of SQLite that recommended updating, or reach a complete resolution to the various refactoring stuff that's being committed into the repository, or someone hits a critical bug, I consider the current release to be both stable and worth letting sit for a while, so there's time for all of downstream to converge. The release of DBD::SQLite::Amalgamation (for me) doesn't add any weight to the need to update. Adam K 2009/7/30 Darren Duncan dar...@darrenduncan.net: I noticed that Audrey released another DBD-SQLite-Amalgamation, after a year of not, that is said to be equivalent to the latest official dev release, citing that it would be redundant once the official release is no longer dev. Considering this, is it reasonable to push an official stable release of some kind now that has 3.6.16, or is it better to continue to wait on that front? -- Darren Duncan ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite ___ DBD-SQLite mailing list DBD-SQLite@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite
