slack-ruby / slack-ruby/slack-ruby-client
Conflict between slack-ruby-client and linux slack executable using rbenv
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.3k
- Forks
- 222
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the gem packaging and executable definitions, then compare how rbenv shims conflict with /usr/bin/slack. The issue presents splitting the client into a separate gem and renaming the executable to slack-cli as possible approaches, so completion requires an agreed resolution to the naming collision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, ruby
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100