ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "Eregon (Benoit Daloze)" <noreply@ruby-lang.org>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:105645] [Ruby master Feature#17760] Where we should install a header file when `gem install --user`?
Date: Fri, 15 Oct 2021 16:25:06 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-94135.20211015162505.482@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17760.20210330005044.482@ruby-lang.org

Issue #17760 has been updated by Eregon (Benoit Daloze).


byroot (Jean Boussier) wrote in #note-8:
> But then I suppose them that compile against `digest.h` would also need to know where to look, I'm really unsure how it's supposed to work. If I have 5 different versions of digest, which one should I compile against?

Because digest is a default gem, I think there is a simple answer here: latest version wins.
That's the behavior of default gems, if you `gem install some_default_gem`, RubyGems will then always use that version (instead of the version shipped with Ruby).

When using bundler, I'd think it's possible to choose an explicit version, and bundler would resolve which one is used.
Probably RubyGems and/or Bundler need to set CPATH to the header is found (seems better), or we need some explicit API in RubyGems and/or mkmf for a gem to ask headers for another gem (seems bad as then we have the version problem).

----------------------------------------
Feature #17760: Where we should install a header file when `gem install --user`?
https://bugs.ruby-lang.org/issues/17760#change-94135

* Author: mrkn (Kenta Murata)
* Status: Third Party's Issue
* Priority: Normal
----------------------------------------
As `digest` have been made a default gem at Ruby 3.0,  it can be installed by `gem install` command.

When we install `digest`, `digest.h` is installed at the same directory as `ruby.h`.  But when we use `gem install --user` for installing it, where should `digest.h` is installed in?

Now, the location of `digest.h` is always the same directory as `ruby.h` regardless of whether we use `gem install --user`.  It occurs permission error when non-root user uses `gem install --user` for installing `digest` on the system-ruby.



-- 
https://bugs.ruby-lang.org/

  parent reply	other threads:[~2021-10-15 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  0:50 [ruby-core:103088] [Ruby master Feature#17760] Where we should install a header file when `gem install --user`? muraken
2021-03-30  0:51 ` [ruby-core:103089] " muraken
2021-03-30 14:20 ` [ruby-core:103101] " nobu
2021-10-14 15:40 ` [ruby-core:105635] " Eregon (Benoit Daloze)
2021-10-15  7:44 ` [ruby-core:105639] " byroot (Jean Boussier)
2021-10-15  8:05 ` [ruby-core:105640] " deivid
2021-10-15 11:01 ` [ruby-core:105642] " byroot (Jean Boussier)
2021-10-15 16:25 ` Eregon (Benoit Daloze) [this message]
2021-10-15 16:30 ` [ruby-core:105646] " Eregon (Benoit Daloze)
2021-10-15 17:16 ` [ruby-core:105647] " byroot (Jean Boussier)
2021-10-21  9:41 ` [ruby-core:105725] " knu (Akinori MUSHA)

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-94135.20211015162505.482@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).