Right now, it's simply a MOTU Developer initiative. Not a concrete / release team approved goal.
I am trying to triange and find packages that:
* depend on sqlite2
* have not been ported to sqlite3 OR do not have sqlite3 equivalent packaged
Binary package asterisk-modules depends on both sqlite2 & 3.
Most of the modules in that package provide both sqlite2 & 3 versions of modules where appropriate.
There is: res_config_sqlite module which links against sqlite2 and there is no res_config_sqlite3 provided.
So if we do decide to drop sqlite2, then there will be loss of functionality (res_config_sqlite module) with no upgrade path, cause there is no res_config_sqlite3 module. Hence this wishlist bug to port that individual module.
Right now, it's simply a MOTU Developer initiative. Not a concrete / release team approved goal.
I am trying to triange and find packages that:
* depend on sqlite2
* have not been ported to sqlite3 OR do not have sqlite3 equivalent packaged
Binary package asterisk-modules depends on both sqlite2 & 3.
Most of the modules in that package provide both sqlite2 & 3 versions of modules where appropriate.
There is: res_config_sqlite module which links against sqlite2 and there is no res_config_sqlite3 provided.
So if we do decide to drop sqlite2, then there will be loss of functionality (res_config_sqlite module) with no upgrade path, cause there is no res_config_sqlite3 module. Hence this wishlist bug to port that individual module.