Re: Ruby Ports I'd Like to Remove

On 09/02 12:49, Stuart Henderson wrote:
> On 2023/09/02 13:43, Rafael Sadowski wrote:
> > On Sat Sep 02, 2023 at 12:33:56PM +0100, Jeremy Evans wrote:
> > > On Sat, Sep 2, 2023 at 12:09???PM Rafael Sadowski <rafael@sizeofvoid.org>
> > > wrote:
> > >
> > > > On Sat Sep 02, 2023 at 09:56:10AM +0000, Jeremy Evans wrote:
> > > > > After going through all of our Ruby ports, I think we should remove the
> > > > > ports listed below. These are a set of leaf ports (some of these ports
> > > > > depend on others in the set, but nothing outside this set depends on
> > > > > something inside this set). These are all pure-ruby ports that don't
> > > > > benefit from packaging.
> > > >
> > > > That means we can install it by using gem(1), correct?
> > > >
> > >
> > > Correct. OpenBSD packages for ruby gems should be equivalent
> > > to what you would get by installing the gem directly.
> > >
> >
> > Perfect, ok to send all of them to Attic. I guess this is going to take
> > a couple of hours and some CVS mistakes :D
>
> we have done way bigger commits than this without screwing up ;)
> the slowest bit is probably writing the quirks entries..

Ruby ports are generally buildable for 3-4 different Ruby versions, so
we generally do not add quirks for removed Ruby ports. Instead, when a
Ruby version goes out of a support, a general quirk is added that
handles all packages for that Ruby version.

Rafael is probably correct that it is going to take a couple of hours.
Hopefully he is wrong about the CVS mistakes, but we'll see. :)

I plan to do the removal on September 6, to give people time to speak
up in case they want to keep any of the ports.

Thanks,
Jeremy