Comment trouver où gem fichiers sont installés

Utilisation joyau de l'environnement à savoir à propos de votre joyau de l'environnement:

RubyGems Environment:
- RUBYGEMS VERSION: 2.1.5
- RUBY VERSION: 2.0.0 (2013-06-27 patchlevel 247) [x86_64-darwin12.4.0]
- INSTALLATION DIRECTORY: /Users/ttm/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0
- RUBY EXECUTABLE: /Users/ttm/.rbenv/versions/2.0.0-p247/bin/ruby
- EXECUTABLE DIRECTORY: /Users/ttm/.rbenv/versions/2.0.0-p247/bin
- SPEC CACHE DIRECTORY: /Users/ttm/.gem/specs
- RUBYGEMS PLATFORMS:
- ruby
- x86_64-darwin-12
- GEM PATHS:
- /Users/ttm/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0
- /Users/ttm/.gem/ruby/2.0.0
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
- https://rubygems.org/
- SHELL PATH:
- /Users/ttm/.rbenv/versions/2.0.0-p247/bin
- /Users/ttm/.rbenv/libexec
- /Users/ttm/.rbenv/plugins/ruby-build/bin
- /Users/ttm/perl5/perlbrew/bin
- /Users/ttm/perl5/perlbrew/perls/perl-5.18.1/bin
- /Users/ttm/.pyenv/shims
- /Users/ttm/.pyenv/bin
- /Users/ttm/.rbenv/shims
- /Users/ttm/.rbenv/bin
- /Users/ttm/bin
- /usr/local/mysql-5.6.12-osx10.7-x86_64/bin
- /Users/ttm/libsmi/bin
- /usr/local/bin
- /usr/bin
- /bin
- /usr/sbin
- /sbin
- /usr/local/bin

Avis les deux sections pour:

• INSTALLATION DIRECTORY
• GEM PATHS

Après l'installation de pierres précieuses, si vous voulez savoir d'où un bijou particulier est. Essayez de taper:

 gem list

Vous serez en mesure de voir la liste des gemmes que vous avez installés. Maintenant utiliser bundle show et le nom de la gemme que vous voulez connaître le chemin, comme ceci:

 bundle show <gemName>

Vous pouvez les consulter sur votre invite de commande en cours d'exécution gem help commands, puis en sélectionnant le bon de commande:

kirti@kirti-Aspire-5733Z:~$  gem help commands
GEM commands are:
build                  Build a gem from a gemspec
cert                   Manage RubyGems certificates and signing settings
check                  Check a gem repository for added or missing files
cleanup                Clean up old versions of installed gems in the local
repository
contents               Display the contents of the installed gems
dependency             Show the dependencies of an installed gem
environment            Display information about the RubyGems environment
fetch                  Download a gem and place it in the current directory
generate_index         Generates the index files for a gem server directory
help                   Provide help on the 'gem' command
install                Install a gem into the local repository
list                   Display gems whose name starts with STRING
lock                   Generate a lockdown list of gems
mirror                 Mirror all gem files (requires rubygems-mirror)
outdated               Display all gems that need updates
owner                  Manage gem owners on RubyGems.org.
pristine               Restores installed gems to pristine condition from
files located in the gem cache
push                   Push a gem up to RubyGems.org
query                  Query gem information in local or remote repositories
rdoc                   Generates RDoc for pre-installed gems
regenerate_binstubs    Re run generation of executable wrappers for gems.
search                 Display all gems whose name contains STRING
server                 Documentation and gem repository HTTP server
sources                Manage the sources and cache file RubyGems uses to
search for gems
specification          Display gem specification (in yaml)
stale                  List gems along with access times
uninstall              Uninstall gems from the local repository
unpack                 Unpack an installed gem to the current directory
update                 Update installed gems to the latest version
which                  Find the location of a library file you can require
yank                   Remove a specific gem version release from
RubyGems.org
For help on a particular command, use 'gem help COMMAND'.
Commands may be abbreviated, so long as they are unambiguous.
e.g. 'gem i rake' is short for 'gem install rake'.
kirti@kirti-Aspire-5733Z:~$ 

Maintenant à partir de ci-dessus, je peux voir la commande environment est utile. Donc, je le ferais:

kirti@kirti-Aspire-5733Z:~$ gem help environment
Usage: gem environment [arg] [options]
Common Options:
-h, --help                       Get help on this command
-V, --[no-]verbose               Set the verbose level of output
-q, --quiet                      Silence commands
--config-file FILE           Use this config file instead of default
--backtrace                  Show stack backtrace on errors
--debug                      Turn on Ruby debugging
Arguments:
packageversion  display the package version
gemdir          display the path where gems are installed
gempath         display path used to search for gems
version         display the gem format version
remotesources   display the remote gem servers
platform        display the supported gem platforms
<omitted>       display everything
Summary:
Display information about the RubyGems environment
Description:
The RubyGems environment can be controlled through command line arguments,
gemrc files, environment variables and built-in defaults.
Command line argument defaults and some RubyGems defaults can be set in a
~/.gemrc file for individual users and a /etc/gemrc for all users. These
files are YAML files with the following YAML keys:
:sources: A YAML array of remote gem repositories to install gems from
:verbose: Verbosity of the gem command. false, true, and :really are the
levels
:update_sources: Enable/disable automatic updating of repository metadata
:backtrace: Print backtrace when RubyGems encounters an error
:gempath: The paths in which to look for gems
:disable_default_gem_server: Force specification of gem server host on
push
<gem_command>: A string containing arguments for the specified gem command
Example:
:verbose: false
install: --no-wrappers
update: --no-wrappers
:disable_default_gem_server: true
RubyGems' default local repository can be overridden with the GEM_PATH and
GEM_HOME environment variables. GEM_HOME sets the default repository to
install into. GEM_PATH allows multiple local repositories to be searched for
gems.
If you are behind a proxy server, RubyGems uses the HTTP_PROXY,
HTTP_PROXY_USER and HTTP_PROXY_PASS environment variables to discover the
proxy server.
If you would like to push gems to a private gem server the RUBYGEMS_HOST
environment variable can be set to the URI for that server.
If you are packaging RubyGems all of RubyGems' defaults are in
lib/rubygems/defaults.rb.  You may override these in
lib/rubygems/defaults/operating_system.rb
kirti@kirti-Aspire-5733Z:~$ 

Enfin vous montrer ce que vous avez demandé, je le ferais:

kirti@kirti-Aspire-5733Z:~$ gem environment gemdir
/home/kirti/.rvm/gems/ruby-2.0.0-p0
kirti@kirti-Aspire-5733Z:~$ gem environment gempath
/home/kirti/.rvm/gems/ruby-2.0.0-p0:/home/kirti/.rvm/gems/ruby-2.0.0-p0@global
kirti@kirti-Aspire-5733Z:~$ 

Vous pouvez tromper gem open dans l'affichage de la gemme chemin:

VISUAL=echo gem open gem-name

Exemple:

VISUAL=echo gem open rails
=> /usr/local/opt/asdf/installs/ruby/2.4.3/lib/ruby/gems/2.4.0/gems/rails-5.1.4