Upstream the SQLCipher & other fixes

[kewde]

Hi,

I'm the maintainer of node-sqlite3 and I'm looking for people interested in helping maintain the original fork. I was wondering if perhaps we could upstream the changes for SQLCipher and other fixes into the original fork and work together in a single repository.

Please let me know if you're interested into verifying the feasibility of such endeavor.

[rkistner]

Hi @kewde,

Thanks for the interest. I agree that it would be good to maintain a single repository instead of multiple forks, but I'm not sure how feasible it is in this case.

The main goal of this fork is to allow using sqlcipher, without requiring custom build flags when installing.

The main changes in this fork are:

1. Use the sqlcipher source instead of sqlite.
2. Adapt the build process to statically link required libraries (openssl mostly).

Then additionally:

• There are some additional tests specific to sqlcipher, and other tests (backups) disabled.
• And the builds all run on CircleCI instead of Travis + AppVeyor (personal preference).

If this is merged into a single repository, we'd still need to do separate sets of native builds, and publish it under separate NPM packages.

I'm open to help with that, but it will require some effort.