Re: git: f45b1d07f50b - main - many: Unsupported Go dep; deprecate and schedule for removal

On Fri, Dec 5, 2025 at 10:54 AM Michael Gmelin <grembo@freebsd.org> wrote:

> (sorry for top posting)
>
> Note:
>
> This should be
>
>   USES= go:modules
>
> otherwise you'll see
>
>   Unknown USES=go,modules
>

Oops, good catch! I *knew* I was going to make that mistake. For some
reason, my fingers always want to put a comma instead of a colon there.

Can I modify, test, and undeprecate ports I depend on, or am I supposed
> to open PRs for each affected port, then wait for a maintainer timeout
> and fix it between Christmas and New Years?


Hi Michael, great thought! Yes, absolutely this should be covered under the
just-fix-it blanket approval.

As for the time-frame, I put 1 month because it's a small number of ports
and it's trivial to test and fix. If people want more time, I'm happy to
extend the expiration date if there is a consensus opinion about what it
should be. I feel pretty strongly that it should be no later than the 1.26
release date.

I think the next step is to set all go 1.24 ports to expire when 1.26 comes
out (at which point 1.24 will be unsupported), which will be
mid-February-ish. Does that sound right?


-- 
Adam Weinberger
adamw@adamw.org // adamw@FreeBSD.org