Hi! On 01.06.22 23:05, Andreas 'Segaja' Schleifer wrote:
On 6/1/22 20:31, Anatol Pomozov wrote:
Hello Andreas
Thank you for your research.
The standard gems are indeed a source of confusion both in Ruby distribution and in Arch packages.
One thing that could really help here is a working proposal with a patch to PKGBUILD. If you can come up with one please file an arch bug and share it with me so I can look at it.
Hi again,
The problem is that in order to get this fully working we need to package all 74 stdlib ruby gems. Currently we have only packaged 9 of them from which 5 are in the AUR.
My proposal to get this into a working state are these steps:
- remove all gems from the ruby package which are already packaged as dedicated packages in [extra] or [community] - create a ruby-stdlib meta package which requires the existing ruby stdlib packages - make the ruby package require the new ruby-stdlib package
I talked to Segaja about this a lot on IRC before he submitted it to the ML. I think this is a very good approach to fix our slightly broken Ruby ecosystem. I also think that the ruby PKGBUILD should be updated before the Ruby 3.1 Rebuild. I'm happy to help packaging the stdlib gems. Cheers, Tim
These steps should clear up the situation for the few existing separate builds of the stdlib packages. Then we can successively package the other stdlib packages and once one is done remove it from the ruby package and add it as dependency to the ruby-stdlib package.
Next week I can prepare the ruby-stdlib package and a patch to the ruby package to get the first steps of this plan working.
Best regards Segaja