Re: Removal of firefox115 and firefox128

["David H. Gutteridge" <david%gutteridge.ca@localhost>]

On Wed, 2026-02-18 at 10:58 +0900, Ryo ONODERA wrote:
> Hi,
> 
> It is relatively hard to fix the build of www/firefox-115 with the
> latest rust toolchain.
> However 128 should be built without problem.
> 
> I would like keep 128 for a while.
> 
> Thank you.

That's true now, but may not be when we get further toolchain
updates. Anyway, if you want to handle it, cool. :)

My other issue is I'm not entirely comfortable with the pkgsrc
approach of leaving in EOL packages that probably (or knowably)
have security issues. I know there's the whole "let the users
decide" philosophy.

I was wanting to keep 115 around before because it was more
performant on older hardware, and still built/worked fine for
a while, though now it's too old to function with some websites.
(Users who want something lightweight that may not work
everywhere are probably best pointed to other packages, anyway.)

> On Wed, Feb 18, 2026, 9:41 David H. Gutteridge <david%gutteridge.ca@localhost>
> wrote:
> > Hi all,
> > 
> > I propose removing firefox115 and firefox128. 115 will be EOL at the
> > end
> > of the month, and has been broken in pkgsrc for months (we move too
> > quickly for some older releases). 128 has been EOL since September
> > 2025,
> > and everyone should have moved to 140, if they wanted to track an
> > ESR
> > here. (I don't know of any compelling reason to keep 128 around.)
> > 
> > I'll remove these in a week or so, if no one objects. (If someone
> > does
> > object, please kindly share what they'd be contributing to keep
> > these
> > packages building as we continue to update LLVM and Rust to new
> > versions, etc.)
> > 
> > Regards,
> > 
> > Dave