vapor
refactor: Rename CSQLite target to VaporCSQLite to avoid downstream conflicts
Due to an issue with SPM and the relative prevalence of C wrappers for SQLite being named CSQLite, it seems prudent/friendly to namespace this target under NIO to reduce the likelihood of target name conflicts with downstream packages.
See: https://github.com/swiftlang/swift-package-manager/issues/8482
I expect this change to be non-breaking and invisible to any downstream packages since it only renames an internal target identifier (not a published product).
The medium term plan for this is to remove the dependency on NIO altogether so I'd prefer to have this named VaporSQLite instead
Why does it matter? We don't expose that target as a linkable product of the package to begin with.
Why does it matter? We don't expose that target as a linkable product of the package to begin with.
@gwynne See the linked issue in swift-package-manager. There's a bug (?) in SPM that will throw name conflict errors even with targets that are not exposed from downstream modules.
The medium term plan for this is to remove the dependency on NIO altogether so I'd prefer to have this named VaporSQLite instead
Made this change.