Possible namespace clash with Hex.pm?

[suranyami]

Possible namespace clash with Hex.pm?

[suranyami]

Okay, so I did the rename, and lo and behold, problem disappears.

How do you want to handle this? There are probably quite a few people already using your library through a github reference in their mix deps, and it wouldn't be good to just break that.

I could make you a collaborator on my renamed fork, and we could take it from there? Leave this repo as it is for backwards compatibility, maybe with a note that it's been renamed and deprecated?

Let me know what you want to do.

[rjsamson]

Yeah, I've been thinking quite a bit about this since elixir introduced Hex a while back, but hadn't yet had a firm reason to make the change yet as it hadn't yet been causing any widespread issues. I'm fine with the name change, and I'm not overly concerned with backwards compatibility since the Elixir community, is I think, somewhat used to breaking changes, and it wouldn't be an issue again going forward. I also like the Hexate name, so go ahead and send a pull request with your changes and I'll merge them in. I'm also happy to add you as a committer / maintainer to this repo (and a maintainer in the package def if you'd like to add that to your pull request.)

Does that sound good to you?

[rjsamson]

Also - maybe could leave a branch as is at this point in time, for anyone that really needed to continue to use the old name for some reason?

[suranyami]

Okay, merged that pull request in, added the pre-rename branch and updated the README.
I don't seem to have permission to rename the repo.

Either you should rename it, or elevate my permissions.

[suranyami]

Also, I think this issue is now resolved!

[rjsamson]

👍 👍 👍

Looks like you already have 'full permissions' - I'm guessing rename and delete are the two things you can't add. Just renamed the repo though. Great work!!

[suranyami]

Excellent! Yeah, I think you need to be the repo's 'owner' to do those.