search

stevenharman / git_tracker

Some simple tricks that make working with Pivotal Tracker even better... and easier... um, besier!
https://github.com/stevenharman/git_tracker
MIT License
170 stars 11 forks source link

git tracker init or git-tracker init ? #17

Closed rpechayr closed 10 years ago

rpechayr commented 10 years ago

Hi,

I think there might be a typo in your readme. git tracker does not seem to be a git command, but the Readme advises users to type git tracker init. It should reead git-tracker init.

Also, for newbyes using rbenv, you might want to recall them to call rbenv rehash after installing git-tracker via gem install.

rpechayr commented 10 years ago

Okay, after reading this, I realize this might be a stupid question ...

stevenharman commented 10 years ago

@rpechayr Is there anything specific I can do to make it easier for folks?

rpechayr commented 10 years ago

I think for now you could just mention the rbenv rehash stuff. A developer of my team had issues with the brew install version. He will create another issue if he can reproduce the problem

stevenharman commented 10 years ago

Interesting. The Homebrew version is the same as the RubyGems version, it's just packaged as a single executable file (no RubyGems dependencies, etc.). Please do open an issue if they can figure out what's misbehaving.

I might argue that folks using rbenv should already be in the habit of rbenv rehash when installing gems with executables. I can appreciate the desire to have instructions in the README, but I hesitate as I don't want to introduce noise by adding instructions for all of the various Ruby managers. Thoughts?

rpechayr commented 10 years ago

Hi. Thank for taking the time to answer this [closed] issue. I will double check what can be the pb w/ brew. About rbenv, you are right but I might also argue that most gems do not install executables (this is btw the reason why it is better to distribute this via homebrew). Rbenv is definitely becoming a standard for ruby gems management. So in my opinion you can well put such a comment, which does not mean you will have to put comments for all systems. As an example, there is no such problem w/ rvm.

Another reason why this rbenv reminder might be worthwhile is that most people (like me yesterday) do not know how to create a git command. They don't know that it relies on an exec in your PATH with the name git-mycommamd. So they might not guess that installs an exec. In addition to that, as you recommend using HB (and again, you are right), people trying the second solution AND using rbenv ANd not running rbenv rehash would not be surprised that it does not work since gem install is not the recommended install procedure.

Envoyé de mon iPhone

Le 23 juil. 2014 à 20:29, Steven Harman notifications@github.com a écrit :

Interesting. The Homebrew version is the same as the RubyGems version, it's just packaged as a single executable file (no RubyGems dependencies, etc.). Please do open an issue if they can figure out what's misbehaving.

I might argue that folks using rbenv should already be in the habit of rbenv rehash when installing gems with executables. I can appreciate the desire to have instructions in the README, but I hesitate as I don't want to introduce noise by adding instructions for all of the various Ruby managers. Thoughts?

— Reply to this email directly or view it on GitHub.