Two third party packages share the same name

SwiftPM uses the last path component of URL as the "identity"; an option to specify explicit dependency names in SE-0226 was rolled back in an amendment due to user confusion.

The reason for not using the package name for package identity was outlined in an amendment to SE-0292, which considered its use as part of a registry service, as follows:

The core team returned SE-0292 for further discussion about package identifiers, but near as I can tell this discussion never reached a resolution as the proposal authors strongly objected to the core team decision. Based on the links in the proposal, no revision of package identifiers along the lines proposed in SE-0292 ever landed.

5 Likes