Hi Andreas, first off: Thanks for looking into this! I guess not all of the packagers knows how complicated and time-consuming packaging ruby can be. On 2022-06-01 23:05:45 (+0200), Andreas 'Segaja' Schleifer wrote:
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.
If you have created a list somewhere and if I have some spare time, I'd be glad to help package some.
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
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.
As the ruby sources will drag in the vendored dependencies it could prove beneficial to have ruby's PKGBUILD carry ruby-stdlib as a split package (unless you think that complicates things). That way it is easy to determine if a new vendored dep is added or removed as well. Best, David -- https://sleepmap.de