Conflict between slack-ruby-client and linux slack executable using rbenv

[kwstannard]

rbenv puts it's shims at the start of PATH, so it blocks access to /usr/bin/slack that comes later in PATH.

Personally, I would suggest splitting the client to a seperate gem that depends on this and renaming the executable to slack-cli to stop the naming collision. I am not using the CLI so I would also be fine with splitting the gems.

[dblock]

I'd be down with splitting the gems and renaming the cli executable there. I don't think I want to do all the work though, so if you're into it @kwstannard, go for it, I can help out with the logistics.

[kwstannard]

Okay. I will see what I can do.

[pocke]

I have the same problem. I'd like to take over the issue.

I have another idea to solve this problem. It is renaming the slack executable file to slack-ruby-client. Linux user can use the CLI with /usr/bin/slack if we choose this idea. And I guess it is easier to maintain than splitting the gem. But it has a little incompatibility. slack command user should switch the command to slack-ruby-client.

What do you think the idea?

[dblock]

I'm fine with this, but i'd prefer we split the tool, too, instead of doing a backwards incompatible rename because it is the best long term solution and reduces the number of dependencies in this project.