Re: Requesting go1.24 in quarterly

You are welcome.

Do you have a poudriere setup? Then I may suggest trying to use go1.24 within quarterly branch so you can see what happens when that port can't find go1.24. 

I don't think that this method is deprecated.

I would just use the default go version without specifying a version in USES flag and it would fetch the right go version.

I'd suggest testing it with poudriere.

I get rid of FreeBSD PKG repositories because I am maintaining some ports and if I already use poudriere, my life gets easier to test my ports. I have a minimalist desktop, though.

Sent from Proton Mail Android


-------- Original Message --------
On 6/21/25 1:07 PM, Stefan Bethke <stb@lassitu.de> wrote:

>  On 21. Jun 2025, at 12:03, Yusuf Yaman <nxjoseph@protonmail.com> wrote:
>  >
>  > On 6/21/25 12:59 PM, Stefan Bethke <stb@lassitu.de> wrote:
>  >
>  >> One of the ports I maintain (www/forgejo) is failing in quarterly because the default version of go there appears to be less than 1.24, and the upstream source build setup will try to install go1.24.
>  >>
>  >> It seems that some time ago ports were clean up to not request specific go versions. How should I address this issue?
>  > I had a port which should have been using go1.24 and that time it wasn't available yet but some time after that, go1.24 was available and the port was set to use go1.24 back then. IIRC, the port was fetching go1.24 in fetch stage when go1.24 wasn't available in ports. I guess that your port can build successfully too by fetching go1.24 toolchain in fetch stage.
>  
>  Thanks, I meant whether it is (still) OK to do USES=go:1.24, or whether this is now deprecated or been replaces with a different mechanism.
>  
>  
>  Stefan
>  
>  --
>  Stefan Bethke <stb@lassitu.de>   Fon +49 175 3288861
>  
>  
>