Luis Padron

@cgrindel What are your thoughts on this issue and how to move it forward? Would the simple workaround of just suffixing the repo with the Bazel module name be enough?...

@cgrindel I like the generate Bazel modules idea and it works for folks who'd like to use SPM as the source of truth (because they primarily have downstream SPM users)...

More discussion on removing need for this file in: https://github.com/cgrindel/rules_swift_package_manager/discussions/743 > It may be as simple as "file_version": X where X is an integer. This will be incremented whenever an...

I can look at fixing that tomorrow if no one else has time, but rules_swift releases are sort of blocked right now as we get some other stuff merged so...

Could/should we flag this in this repo based on the swift tools version of the Package.swift?

@watt @cgrindel Brentley and I discussed a lil and it probably makes more sense to gate the setting of `package_name` in this repository and not in rules_swift. Reasoning being SPM...

Yeah I imagine that's how it works in SPM but haven't checked

This is a minimal BUILD file it seems we would need to get something like `CSQLite` generated (this is used in GRDB.swift for example): ```starlark load("@rules_cc//cc:defs.bzl", "cc_library") load("@build_bazel_rules_swift//swift:swift.bzl", "swift_library_group", "swift_interop_hint")...

We've hit this a few times, definitely still an issue +1. Only a restart seems to fix in the cases we've hit.

This is easily reproducible on macOS if you log out and log back in after having made a build. It seems the bazel server doesn't handle this well