From: Stefan Schmiedl <s@xss.de>
To: Peter Humphrey <peter@prh.myzen.co.uk>, gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Permissions problem
Date: Tue, 15 Aug 2023 18:38:20 +0200 [thread overview]
Message-ID: <587907205.20230815183820@xss.de> (raw)
In-Reply-To: <13353429.uLZWGnKmhe@wstn>
Dienstag, 15. August 2023 16:55:
> Hello list,
> I'd like to develop a blog using www-apps/jekyll, which makes extensive use of
> ruby gems, of which I have no experience. On trying to install a new default
> theme I get copious permission errors.
> The ruby gems live in /usr/lib64/ruby/gems/3.1.0/gems, and to install anything
> in that tree I need write permission on the destination directory and execute
> permission on all those above it.
> This poses an obvious security problem.
> When I emerged jekyll and ran its installation routine, I found I had a new ~/
> bin directory with nine executable files in it. ~/bin/update_rubygems has
> similar permission problems but is more concise in reporting them
> I can't add myself to a group and grant it permissions, because there seems
> not to be any such group.
> How do Gentoo Ruby users get around this?
Hello Peter,
first make sure that you don't have any "suspicious" rubygem based
executables in your path that might confuse things. Some time ago
I found some ancient such files in /usr/local/bin ...
Next, with a default ruby/rubygems installation, a normal user should
be able to install gems into their own $HOME/.gem directory. I'm doing
this on several gentoo boxes, never had a problem with that approach.
On one of the servers, I can run the following command, to which you can
compare your environment
$ gem environment
RubyGems Environment:
- RUBYGEMS VERSION: 3.3.26
- RUBY VERSION: 3.1.4 (2023-03-30 patchlevel 223) [x86_64-linux]
- INSTALLATION DIRECTORY: /usr/lib64/ruby/gems/3.1.0
- USER INSTALLATION DIRECTORY: /home/.../.gem/ruby/3.1.0
- RUBY EXECUTABLE: /usr/bin/ruby31
- GIT EXECUTABLE: /usr/bin/git
- EXECUTABLE DIRECTORY: /usr/bin
- SPEC CACHE DIRECTORY: /home/.../.gem/specs
- SYSTEM CONFIGURATION DIRECTORY: /etc
- RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
- GEM PATHS:
- /usr/lib64/ruby/gems/3.1.0
- /home/.../.gem/ruby/3.1.0
- /usr/local/lib64/ruby/gems/3.1.0
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => true
- :bulk_threshold => 1000
- "install" => "--install-dir /home/.../.gem/ruby/3.1.0 --bindir /home/.../bin"
- "uninstall" => "--install-dir /home/.../.gem/ruby/3.1.0 --bindir /home/...bin"
- "update" => "--install-dir /home/.../.gem/ruby/3.1.0 --bindir /home/.../bin"
- REMOTE SOURCES:
- https://rubygems.org/
- SHELL PATH:
- /usr/local/sbin
- /usr/local/bin
- /usr/sbin
- /usr/bin
- /sbin
- /bin
- /opt/bin
next prev parent reply other threads:[~2023-08-15 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 14:55 [gentoo-user] Permissions problem Peter Humphrey
2023-08-15 16:38 ` Stefan Schmiedl [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-05 0:39 [gentoo-user] permissions problem John Jolet
2006-02-05 1:56 ` Richard Fish
2006-02-05 2:24 ` John Jolet
2006-02-05 2:59 ` Jerry McBride
2006-02-05 6:58 ` Richard Fish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=587907205.20230815183820@xss.de \
--to=s@xss.de \
--cc=gentoo-user@lists.gentoo.org \
--cc=peter@prh.myzen.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox