sqlcipher 4.11.0

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

release notes

**Full Changelog**: https://github.com/sqlcipher/sqlcipher/compare/v4.10.0...v4.11.0

View the full release notes at https://github.com/sqlcipher/sqlcipher/releases/tag/v4.11.0.

---

[chenrui333]

• https://github.com/Homebrew/homebrew-core/pull/216529
• https://github.com/Homebrew/homebrew-core/pull/221742
• https://github.com/Homebrew/homebrew-core/pull/223614
• https://github.com/Homebrew/homebrew-core/pull/232358

[cho-m]

We still need to decide on https://github.com/Homebrew/homebrew-core/pull/216529#issuecomment-2751706724

sqlcipher was originally forked from sqlite, and with this release, they have moved to shadow sqlite bin and lib names, sqlite3 and libsqlite3.{a,so,dylib}. A few ways I can think of us navigating this:

• Rename build outputs back to the old names, then provide shadowed names in some other directory, kind of like gnubin

  • I don't think upstream provides a way to configure the install name easily
  • Not sure what are the implications of merely renaming a so/dylib (need to adjust install name/soname too?)

• Mark as conflict with sqlite3 formula

  • Maybe need to set as keg_only :provided_by_macos too?
  • If proceeding with this route, make changes insqlite3 formula here or in a new PR? We probably don't want/need ot rebuild sqlite3 bottles for this

[gromgit]

My 2 cents: keep SQLite and SQLCipher separate, since the latter is a fork that explicitly maintains upstream's API while adding new features, so a lot of programs would only fail at runtime if accidentally linked against original SQLite.

Anyway, at least one distro has gone the renaming route, so there's already an example of what to do. I'm not sure it's perfect, but it's a starting point.