You are not logged in.
Pages: 1
Topic closed
This is weird. My Arch installation is more than four years old. For almost all of that time, I have used irb. Today I tried to use it and received "command not found".
I searched the packages database and found that package ruby-irb was updated on Jan-11-19. So, I searched my pacman.log (which goes all the way back to Dec-26-14) and there were no occurrences of string ruby-irb, nor of string irb for that matter. So, I conclude that nothing removed irb, and I know that I have used it for years.
I installed package ruby-irb and I can now use irb, again. But, what happened to the irb I've used for years?
Last edited by ratcheer (2019-01-12 22:54:35)
Offline
Offline
Ok, thank you. I doubt that many normal users saw that. Even the packager, himself says he "forgot to mention" it.
Last edited by ratcheer (2019-01-12 22:53:48)
Offline
Well it was posted to arch-general...
Offline
Same questions here. Submitted edit to Arch Ruby Wiki to reflect this.
Offline
Hi!
I'm a rubygems & bundler maintainer, and ruby-core casual contributor. The change made in the archlinux ruby package is incorrect. The _development_ of the irb functionality has indeed been moved to a separate repository, but the functionality should still be bundled by default with ruby, and every ruby user expects that. The only reason to move irb to a separate repo is to increase visibility and lower the contribution barrier, but nothing should change regarding packaging.
To expand a bit more on this. Ruby-core has two types of builtin functionality:
* Default gems: These are always provided by default. You only need to load them, and they should just work on any ruby installation. You don't even need to use the concept of a "ruby package" (gem) to use them, since they live inside the core installation. IRB is one of these libraries.
* Bundled gems: These are regular packages that ruby-core installs by default.
I think ruby developers _might_ understand that some distributions choose to not ship some "bundled gems" by default, but the set of "default gem" functionality should always be provided since it's the basic set of libraries that the ruby community considers as the core of ruby.
There's more information about all this here: https://stdgems.org/.
So, I'd like to request the removal of IRB to be reverted, or `ruby-irb` added as a dependency of the `ruby` package.
I opened a ticket about this: https://bugs.archlinux.org/task/62709?p … &sort=desc. I'm happy to help with getting this fixed.
Offline
Thanks for sharing your insights, deivid.rodriguez. Since you've already opened a bug on the bug tracker and linked to it here, I'm going to go ahead and close this topic so that the discussion can move to the more appropriate location.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1
Topic closed