Name collision

[nikolay]

I'm working on a project called anyenv, which is in the same space, but different. I registered domains, etc. Why did you change from everyenv to anyenv?

[nikolay]

There seems to be another project, kinda similar to yours, under the same brand: https://github.com/riywo/anyenv

[mislav]

I'm not terribly attached to my name, but I don't have much better ideas. Since we're not talking about registered trademarks or "brands" necessarily, I think it's OK that some projects share a name.

Thanks for bringing @riywo's work to my attention. I was trying to compile a list of rbenv-inspired projects last night and didn't know that someone already has a comprehensive list and wrote tool to manage them all. (A manager for version managers? So meta!) 👏

As a matter of fact, I planned to stir this project in the direction that aforementioned anyenv already took— consolidating all version managers' ROOT directories under a shared location, and setting up all of their shims paths in one init call instead of a separate shell configuration for every *env tool.

[riywo]

Interesting! I wrote my anyenv two years ago.

Here is github.com, where you can use any name space under your account. For example, there are many phpenv repositories. So, I think we can keep our own "anyenv" project on github.com and that could be a normal case.

The name space will be conflicted in other services such as DNS, rubygems, etc. Then, we or some other guys should discuss about the name at the service.

[mislav]

Thanks @riywo. I've looked at your code and I've found that you've implemented the shared root for all the version managers in a similar manner that I have planned to as well. I may draw some inspiration from your code later.

[jasonkarns]

@mislav did you ever compile a list of rbenv-inspired projects somewhere?

[mislav]

@jasonkarns yes https://gist.github.com/mislav/116ba3305b6a2974980f