State of ruby ecosystem in conda-forge

[h-vetinari]

No-one has been touching the ruby ecosystem for a while. There's an open migration to ruby 3.x that started over half a year ago and has immediately run into blockers that have gone unresolved since then.

Ruby <3.0 is also incompatible with OpenSSL 3, which has been our default since January.

Ruby itself has a bunch of downloads, but it seems the other packages are pretty dead.

What - if anything - are we going to do about this? @conda-forge/ruby

CC @conda-forge/core

[traversaro]

Personally I am interested in ruby itself as it is a dependency for some packages I mantain (mainly https://github.com/conda-forge/libsdformat-feedstock/ and https://github.com/conda-forge/gz-tools2-feedstock). While in the long term the dependency will be dropped (see gazebosim/sdformat#274 and gazebosim/gz-tools#7) in the short/medium term I need to depend on it, so if necessary I will be happy to mantain the ruby feedstock. On the other hand, I am not particularly interested in any gem/other ruby-related packages.

Based on conda-forge/ruby-feedstock#122, perhaps @lmrodriguezr could be interested in this discussion?

[wolfv]

I think it would be great to have ruby itself well supported in conda-forge. I am not sure if we have the man-power / interest for the packages from the ruby ecosystem though (although I ran into some compilation problems when using some ruby packages that needed C extensions in the past ... )

[lmrodriguezr]

Indeed, I'd be interested, thanks for tagging @traversaro !

I would agree with @wolfv , ruby itself is probably the only mission-critical part. Any packages could be installed on top of it with not a lot of effort. I've also encountered some issues installing native packages in the past, but recent forge versions seem to be pretty stable