From 1fcb9881648c902d72556e3becde73790f4dbcfc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mislav=20Marohni=C4=87?= Date: Fri, 5 Jul 2024 14:39:31 +0200 Subject: [PATCH] readme: add some warnings --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 676664c..69ea17d 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,8 @@ On systems with Homebrew package manager, the “Using Package Managers” metho #### Debian, Ubuntu, and their derivatives - Note that the version of rbenv that is packaged and maintained in the + > [!CAUTION] + > The version of rbenv that is packaged and maintained in official Debian and Ubuntu repositories is _out of date_. To install the latest version, it is recommended to [install rbenv using git](#basic-git-checkout). @@ -144,7 +145,7 @@ Select a Ruby version for your project using `rbenv local 3.1.2`, for example. T gem install bundler ``` -> [!WARNING] +> [!NOTE] > You _should not use sudo_ to install gems. Typically, the Ruby versions will be installed under your home directory and thus writeable by your user. If you get the “you don't have write permissions” error when installing gems, it's likely that your "system" Ruby version is still a global default. Change that with `rbenv global ` and try again. Check the location where gems are being installed with `gem env`: