possibly off-topic as it likely applies to other linux distros, but i'm diving into ruby and i'm well aware that if i install, say, vagrant, it comes with a pile of rubygem dependencies:
Installing: vagrant noarch 2.2.9-3.fc33 fedora 572 k Installing dependencies: bsdtar x86_64 3.5.1-1.fc33 updates 65 k rubygem-childprocess noarch 1.0.1-6.fc33 fedora 60 k rubygem-domain_name noarch 0.5.20190701-3.fc33 fedora 53 k rubygem-erubis noarch 2.7.0-23.fc33 fedora 39 k rubygem-ffi x86_64 1.12.1-3.fc33 fedora 106 k rubygem-fog-libvirt noarch 0.7.0-3.fc33 fedora 33 k ... etc etc ...
fair enough, but is there any effect from personally installing any of those ruby gems using "gem install"? if i install ruby gems as a regular user, they get planted under ~/.gem/..., but i assume those are not taken into account when i'm installing vagrant.
on the other hand, if i install (as root) a gem using "gem install" under /usr/share/gems, will the install process take that into account?
rday
On 3/12/21 2:28 PM, Robert P. J. Day wrote:
possibly off-topic as it likely applies to other linux distros, but i'm diving into ruby and i'm well aware that if i install, say, vagrant, it comes with a pile of rubygem dependencies:
Installing: vagrant noarch 2.2.9-3.fc33 fedora 572 k Installing dependencies: bsdtar x86_64 3.5.1-1.fc33 updates 65 k rubygem-childprocess noarch 1.0.1-6.fc33 fedora 60 k rubygem-domain_name noarch 0.5.20190701-3.fc33 fedora 53 k rubygem-erubis noarch 2.7.0-23.fc33 fedora 39 k rubygem-ffi x86_64 1.12.1-3.fc33 fedora 106 k rubygem-fog-libvirt noarch 0.7.0-3.fc33 fedora 33 k ... etc etc ...
fair enough, but is there any effect from personally installing any of those ruby gems using "gem install"? if i install ruby gems as a regular user, they get planted under ~/.gem/..., but i assume those are not taken into account when i'm installing vagrant.
on the other hand, if i install (as root) a gem using "gem install" under /usr/share/gems, will the install process take that into account?
Nothing that you install outside of rpm will be visible to dnf. It will still pull all those dependencies. It should work the other way though. Any rpm gems you install should be visible to the ruby installer.
On Fri, 12 Mar 2021, Samuel Sieb wrote:
On 3/12/21 2:28 PM, Robert P. J. Day wrote:
possibly off-topic as it likely applies to other linux distros, but i'm diving into ruby and i'm well aware that if i install, say, vagrant, it comes with a pile of rubygem dependencies:
Installing: vagrant noarch 2.2.9-3.fc33 fedora 572 k Installing dependencies: bsdtar x86_64 3.5.1-1.fc33 updates 65 k rubygem-childprocess noarch 1.0.1-6.fc33 fedora 60 k rubygem-domain_name noarch 0.5.20190701-3.fc33 fedora 53 k rubygem-erubis noarch 2.7.0-23.fc33 fedora 39 k rubygem-ffi x86_64 1.12.1-3.fc33 fedora 106 k rubygem-fog-libvirt noarch 0.7.0-3.fc33 fedora 33 k ... etc etc ...
fair enough, but is there any effect from personally installing any of those ruby gems using "gem install"? if i install ruby gems as a regular user, they get planted under ~/.gem/..., but i assume those are not taken into account when i'm installing vagrant.
on the other hand, if i install (as root) a gem using "gem install" under /usr/share/gems, will the install process take that into account?
Nothing that you install outside of rpm will be visible to dnf. It will still pull all those dependencies. It should work the other way though. Any rpm gems you install should be visible to the ruby installer.
i assumed as much, just wondered whether there was some weird, sophisticated subtlety i was unaware of.
rday
-
Robert P. J. Day -
Samuel Sieb