From: "Eregon (Benoit Daloze)" Date: 2021-10-15T16:30:41+00:00 Subject: [ruby-core:105646] [Ruby master Feature#17760] Where we should install a header file when `gem install --user`? Issue #17760 has been updated by Eregon (Benoit Daloze). byroot (Jean Boussier) wrote in #note-8: > e.g. I have `app1` with `digest 3.0.0` and `app2` with `digest 3.2.0`, both have `somegem-that-link-to-digest`, this means we'd need to compile that gem twice and link against different headers? This is a good point. Maybe it can be resolved by `somegem-that-link-to-digest` depending on an exact version (or small range of versions) of digest which have the same header and fully compatible (both forward and backward between all those versions)? I.e., the header is also part of API (or technically ABI) so if `digest` changes the header in some incompatible way (including what gets generated by gems using it), then it should bump the major version (or some other well-documented scheme). > Seems complicated. Maybe I should put this to the next developers meeting agenda. Yes, I think that would be useful. ---------------------------------------- Feature #17760: Where we should install a header file when `gem install --user`? https://bugs.ruby-lang.org/issues/17760#change-94136 * 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/ Unsubscribe: