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
> > > wrote:
> > >
> > > > On Sat Sep 02, 2023 at 09:56:10AM +, Jeremy Evans 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
> > wrote:
> >
> > > On Sat Sep 02, 2023 at 09:56:10AM +, Jeremy Evans wrote:
> > > > After going through all of our Ruby ports, I thi
On Sat Sep 02, 2023 at 12:33:56PM +0100, Jeremy Evans wrote:
> On Sat, Sep 2, 2023 at 12:09 PM Rafael Sadowski
> wrote:
>
> > On Sat Sep 02, 2023 at 09:56:10AM +, Jeremy Evans wrote:
> > > After going through all of our Ruby ports, I think we should remove the
> > > ports listed below. These
On Sat, Sep 2, 2023 at 12:09 PM Rafael Sadowski
wrote:
> On Sat Sep 02, 2023 at 09:56:10AM +, 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
On Sat Sep 02, 2023 at 09:56:10AM +, 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
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 pack