I have prepared a first draft of a pull request to update to SQLitePCLRaw 3.x, but as I was preparing to open that PR, I saw an indication that I should coordinate with an issue first. So here is that issue.
Shall I proceed with that PR?
More background:
SQLitePCLRaw 3.x is entirely about changes in packaging -- it includes no functional code changes. In the most basic sense, when using the SQLitePCLRaw.bundle_e_sqlite3 package, the PR is just updating from version 2.1.11 to 3.0.1.
However, there are a few other packaging changes which affect the test suites here, and that makes the PR a little more complicated.
-
I am no longer publishing crypto enabled SQLite builds (e_sqlcipher and e_sqlite3mc) at no cost. So my PR removes those test projects from the sln file.
-
Two other bundles have also been removed from SQLitePCLRaw 3.x, including .bundle_sqlite3 (used for the OS-provided SQLite on systems like Linux and Mac), and .bundle_winsqlite3 (used for the OS-provided SQLite on Windows). The underlying provider functionality is still there -- only the bundle packages are removed, because they cause confusion, and they are essentially an entire package for one line of initialization code. So I have removed these from the sln file as well, but they could be brought back by using the provider directly. I was going to structure the PR that way, but for some reason, the relevant packages are not available in the package sources used by this repo, even though they are on nuget.org.
I have prepared a first draft of a pull request to update to SQLitePCLRaw 3.x, but as I was preparing to open that PR, I saw an indication that I should coordinate with an issue first. So here is that issue.
Shall I proceed with that PR?
More background:
SQLitePCLRaw 3.x is entirely about changes in packaging -- it includes no functional code changes. In the most basic sense, when using the
SQLitePCLRaw.bundle_e_sqlite3package, the PR is just updating from version 2.1.11 to 3.0.1.However, there are a few other packaging changes which affect the test suites here, and that makes the PR a little more complicated.
I am no longer publishing crypto enabled SQLite builds (e_sqlcipher and e_sqlite3mc) at no cost. So my PR removes those test projects from the sln file.
Two other bundles have also been removed from SQLitePCLRaw 3.x, including
.bundle_sqlite3(used for the OS-provided SQLite on systems like Linux and Mac), and.bundle_winsqlite3(used for the OS-provided SQLite on Windows). The underlying provider functionality is still there -- only the bundle packages are removed, because they cause confusion, and they are essentially an entire package for one line of initialization code. So I have removed these from the sln file as well, but they could be brought back by using the provider directly. I was going to structure the PR that way, but for some reason, the relevant packages are not available in the package sources used by this repo, even though they are on nuget.org.