Date: Sat, 11 Apr 2026 13:20:20 +0200 From: Daniel Engberg <diizzy@FreeBSD.org> To: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 5a812cabd355 - main - math/lcalc: upgrade to 2.2.1 Message-ID: <b6bfed13-74df-41c1-9e13-5d3ba5567048@FreeBSD.org> In-Reply-To: <adopmEYwcvCrA4Az@alien> References: <69d9665e.18aa0.3624ee8c@gitrepo.freebsd.org> <57dd2ca6-afbb-4f53-ba1b-dff142bde573@FreeBSD.org> <adopmEYwcvCrA4Az@alien>
index | next in thread | previous in thread | raw e-mail
On 2026-04-11 12:59, Thierry Thomas wrote: > Le sam. 11 avr. 26 à 5:23:45 +0000, Daniel Engberg <diizzy@FreeBSD.org> > écrivait : > >> Why? Release archive is supplied by upstream >> https://gitlab.com/sagemath/lcalc/-/releases >> https://gitlab.com/-/project/12934202/uploads/0bcf82cdd02412faf9ec0cf80e656610/lcalc-2.2.1.tar.xz > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > This kind of URL is unpredictable, and portscout won’t be able to detect > the next release. Dynamically generated archives breaks (we've seen it multiple times), is discouraged and on top of that you add quite a bit more build dependencies for no benefit (in terms of packaging). It makes more sense to have a working build rather than Portscout being "broken", fwiw it already fails on a ton of ports (reports available) and is ~unmaintained. Long term we should probably look into migrating to another tool such as nvchecker but that's another topic. Best regards, Danielhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b6bfed13-74df-41c1-9e13-5d3ba5567048>