DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=mz3ntFYazU2eK60f85L6wCZ8iYRhX
	wqMg91QOh0Ct/wMihP9AZRh1TyryYr0YuhkZizkOozk1O5gWLp6RYgFDGaztxrpS
	IwO+y0pyaiBMku8UHjOLIuoywzb+iKTOaBmjIgZ884bx8XLnUkeOu/AKpyjbagOG
	IBmHN4VKOvqHCo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
Date: Sat, 15 Nov 2014 08:38:59 +0100
Message-ID: <CAHfREDWPfGmb-iKUpVwPKw5FBmZAFR4kjtbsZKBUZysX2GwOUg@mail.gmail.com>
Subject: Ruby issue: Installed gems are not in path
From: Tallak Tveide <tallak@tveide.net>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

When installing gems with the packaged Ruby, any command line binaries
that are included with installed gems are not available in the path.

When the gems have previously (meaning in an earlier installed version
of Ruby) been installed, they work as expected. I suspect this is
because the binaries in /usr/bin/xxx are already present before
installing the gem anew.

I have seen the same behavior on a colleage's machine

Example:

$ gem install t
Fetching: simple_oauth-0.3.0.gem (100%)
Successfully installed simple_oauth-0.3.0
Fetching: naught-1.0.0.gem (100%)
Successfully installed naught-1.0.0
<lots more output>
$ t
-bash: t: command not found

$ ruby --version
ruby 2.0.0p594 (2014-10-27) [i386-cygwin]

$ uname -a
CYGWIN_NT-6.1-WOW64 NOR-4911GS1 1.7.33-2(0.280/5/3) 2014-11-13 15:45 i686 Cygwin

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple