Date: Sat, 21 Jun 2025 12:06:50 +0200 From: Stefan Bethke <stb@lassitu.de> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Requesting go1.24 in quarterly Message-ID: <ED1F8001-3153-477F-BBCB-F53E5445001D@lassitu.de> In-Reply-To: <yarNerHWL_7Sn0zhw447hAUpzcVAl_vqVi0uU06scFGwMuO1EA77E2g09aVyGhywNk5N9UfN0pNOLzB0IdQJ9Xug1WFsy5lKFwBbQimGePM=@protonmail.com> References: <5D53ED2E-FD6A-4F15-A0EA-7041E5795977@lassitu.de> <yarNerHWL_7Sn0zhw447hAUpzcVAl_vqVi0uU06scFGwMuO1EA77E2g09aVyGhywNk5N9UfN0pNOLzB0IdQJ9Xug1WFsy5lKFwBbQimGePM=@protonmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21. Jun 2025, at 12:03, Yusuf Yaman <nxjoseph@protonmail.com> wrote: >=20 > On 6/21/25 12:59 PM, Stefan Bethke <stb@lassitu.de> wrote: >=20 >> 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. >>=20 >> 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=3Dgo:1.24, or = whether this is now deprecated or been replaces with a different = mechanism. Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 175 3288861
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ED1F8001-3153-477F-BBCB-F53E5445001D>