Date: Tue, 14 Oct 2025 15:44:52 +0000 From: bugzilla-noreply@freebsd.org To: go@FreeBSD.org Subject: [Bug 290231] lang/go124: silence portscout Message-ID: <bug-290231-42334-fZwyBzH9jt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-290231-42334@https.bugs.freebsd.org/bugzilla/> References: <bug-290231-42334@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D290231 Adam Weinberger <adamw@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress CC| |adamw@FreeBSD.org Flags|maintainer-feedback?(go@Fre |maintainer-feedback+ |eBSD.org) | --- Comment #1 from Adam Weinberger <adamw@FreeBSD.org> --- THANK YOU! This has been on my list for forever. Yes, please, commit it. (I= can only sortof imagine what the variable reorganization will look like, but I'= ll take your word for it that it's better.) Plus, I just bumped Go ports, so we're going to get a new round of warnings= , so this came at a great time. But, instead of hardcoding a limiter in each port, I'd much rather that we construct that variable programmatically and put it into go-devel/Makefile,= so that it's shared by all current and future go ports. Any interest in buildi= ng that as a follow-up? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290231-42334-fZwyBzH9jt>