Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We should probably check for duplicates #517

Open
JJ opened this issue Jul 13, 2020 · 2 comments
Open

We should probably check for duplicates #517

JJ opened this issue Jul 13, 2020 · 2 comments

Comments

@JJ
Copy link
Contributor

JJ commented Jul 13, 2020

If I got this right, someone uploading a distribution that provides Foo::Bar will name-clash with another distribution whose name is Foo:Bar or simply provides that module too. So we should issue a warning stating that fact, or maybe thrown an error.

@nxadm
Copy link
Contributor

nxadm commented Jul 13, 2020

Isn't that something by design? Luckily, Raku does not use the hierarchical CPAN module flow and allows differentiation by author name and version. It is a major selling point.

Warning for a core feature will be read as a discouragement and cause more confusion. Could adding the author repo handle (e.g. from github) to the importable name space be a solution?

@JJ
Copy link
Contributor Author

JJ commented Jul 13, 2020

Well, the core feature is that you can add auth as metadata. Warnings will be issued if you don't, because, as far as I understand it, the one with the newer version will be used. The way I understand it, if two distributions provide Foo::Bar, you have to explicitly declare Foo::Bar:auth in the module if you want it to be used that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants