diff options
| author | Jonathan Ringer <jonringer117@gmail.com> | 2021-10-22 09:33:07 -0700 |
|---|---|---|
| committer | Jonathan Ringer <jonringer117@gmail.com> | 2021-10-22 09:33:07 -0700 |
| commit | fc25d940101161034ac357c48a5912b413fa75cc (patch) | |
| tree | 8d704fee8fa5137952e12e19d74e683ce1fea729 /doc/languages-frameworks | |
| parent | 54a42ab84624e64ad5a1f34daa9559d148970f95 (diff) | |
| parent | 1cab3e231b41f38f2d2cbf5617eb7b88e433428a (diff) | |
| download | nixpkgs-fc25d940101161034ac357c48a5912b413fa75cc.tar nixpkgs-fc25d940101161034ac357c48a5912b413fa75cc.tar.gz nixpkgs-fc25d940101161034ac357c48a5912b413fa75cc.tar.bz2 nixpkgs-fc25d940101161034ac357c48a5912b413fa75cc.tar.lz nixpkgs-fc25d940101161034ac357c48a5912b413fa75cc.tar.xz nixpkgs-fc25d940101161034ac357c48a5912b413fa75cc.tar.zst nixpkgs-fc25d940101161034ac357c48a5912b413fa75cc.zip | |
Merge remote-tracking branch 'origin/master' into staging-next
Conflicts: pkgs/development/python-modules/jupyter-client/default.nix pkgs/development/python-modules/jupyterlab-git/default.nix
Diffstat (limited to 'doc/languages-frameworks')
| -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 36b794458cb..5e2f72ed61e 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. |