diff options
| author | Sergei Trofimovich <slyich@gmail.com> | 2021-10-20 21:29:18 +0100 |
|---|---|---|
| committer | Sergei Trofimovich <slyich@gmail.com> | 2021-10-22 08:46:57 +0100 |
| commit | c6b949c09c791e6fe4d88d5c0971fdce83a22268 (patch) | |
| tree | ffa5492e5da5b8d7497d831b5a229828c068b4c5 /doc | |
| parent | 3ef1d2a9602c18f8742e1fb63d5ae9867092e3d6 (diff) | |
ruby_2_6, rubyPackages_2_6: drop unused package
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/languages-frameworks/ruby.section.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/languages-frameworks/ruby.section.md b/doc/languages-frameworks/ruby.section.md index 36b794458cba9..5e2f72ed61ec7 100644 --- a/doc/languages-frameworks/ruby.section.md +++ b/doc/languages-frameworks/ruby.section.md @@ -8,7 +8,7 @@ In the Nixpkgs tree, Ruby packages can be found throughout, depending on what th There are two main approaches for using Ruby with gems. One is to use a specifically locked `Gemfile` for an application that has very strict dependencies. The other is to depend on the common gems, which we'll explain further down, and rely on them being updated regularly. -The interpreters have common attributes, namely `gems`, and `withPackages`. So you can refer to `ruby.gems.nokogiri`, or `ruby_2_6.gems.nokogiri` to get the Nokogiri gem already compiled and ready to use. +The interpreters have common attributes, namely `gems`, and `withPackages`. So you can refer to `ruby.gems.nokogiri`, or `ruby_2_7.gems.nokogiri` to get the Nokogiri gem already compiled and ready to use. Since not all gems have executables like `nokogiri`, it's usually more convenient to use the `withPackages` function like this: `ruby.withPackages (p: with p; [ nokogiri ])`. This will also make sure that the Ruby in your environment will be able to find the gem and it can be used in your Ruby code (for example via `ruby` or `irb` executables) via `require "nokogiri"` as usual. |