On 08/25 01:25, Jeremy Evans wrote: > I haven't started runtime tests of each Ruby port. I think it's likely > there will runtime problems in some of them. I think in most cases, > problems will be solvable by upgrading to newer versions. In some > cases, we may need to keep them on ruby 2.7. I'll start work on > runtime testing shortly.
I did some basic runtime testing of all ruby30-* ports. As expected, I found some issues. Some I've fixed today, others I've emailed maintainers about. There are a few ports that I recommend sending to the Attic. Most have been broken for some time: net/ruby-agcaldav: Won't load on ruby 3.0 or 2.7, due to "undefined method `ical_component' for Icalendar::Event:Class". That was removed in ruby-icalendar 2.0.0, so this port has been broken at runtime since ruby-icalendar was upgraded to 2.1.0 in July 2014. No reverse dependencies. devel/ruby-racc: Won't install on ruby 3.0 due to conflicts with lang/ruby/3.0, not needed in ruby 2.6 or 2.7 as the same or newer version is shipped with ruby. No reverse dependencies. www/ruby-mechanize: Imported in 2009, untouched since. Requires iconv at runtime, which was removed in Ruby 2.0, so this has been broken since then. Last updated in 2009. No reverse dependencies except geo/ruby-findmyiphone. geo/ruby-findmyiphone: Depends on www/ruby-mechanize. Since it depends on mechanize, probably broken since Ruby 2.0. Last updated in 2015. No reverse dependencies. devel/ruby30-gir_ffi: Doesn't load on Ruby 2.6, 2.7, or 3.0 (Could not open library '/usr/local/lib/girepository-1.0': File not an ELF object.). No reverse dependencies. Last updated in 2015. OK to remove these 5 ports? Thanks, Jeremy
