URLs as Swift Package Identifiers

[mattt]

@michelf

Reading this very long thread, I still don't understand why this:

com.github.michelf.mypackage

would be more of an issue than this:

github.com/michelf/mypackage

as unique identifier. The domain name system is the central naming authority in both cases.

Because com.github.michelf.mypackage can't route a package without a registry.

@Frizlab

Hardly, like @John_McCall said. Actually that is my main issue w/ SPM today and the reason I wanted to chime in on this proposal.

I’ve been bit by that once. Consider the following graph:
A depends on B and C , and B depends on C .
Then you change C ’s URL in A ’s Package.swift (just the source URL, the package is the same), but not in B ’s.
When resolving packages, SPM is lost (or at least was when I last tried).

You'll run into the same problem with opaque identifiers as well, except that now you'll have to reason with the extra level of indirection created by a registry.