Date: Mon, 08 Jun 2026 04:22:39 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 295927] lang/gnat1?: PREVASSET does not work Message-ID: <bug-295927-7788@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295927 Bug ID: 295927 Summary: lang/gnat1?: PREVASSET does not work Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: agh@riseup.net Using PREVASSET does not work because the Makefile is fixed to the previous version of the Port, however, if a user wants to use the built assets from the Port, via the option ASSETS, which is enabled by default, simply updating distinfo is not enuf, because the Makefile does not honor ${DISTVERION} via ${_PREV_ASSET_VER}. So using the option PREVASSET will not find the newly built asset that matches the current ${DISTVERSION}. Would it not be better to enable the user to use locally built assets without modifying the port's Makefile? The Port already has a previous GNAT versions for bootstrapping, and it seems both PREVASSET and GNAT bootstrap are currently the same. If the Port can be bootstrapped with the version prior, than why does that have to be coded in PREVASSET, would it not be better to have have previous assets reflect the current port's version, and not the the bootstrapped version? I noticed this while working on GNAT-15 and 16, and I thought this was possible when GNAT-12 was initially committed. So another possible reason is having PREVASSET reflect the current version enables easier bootstrapping of the next version of GNAT. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-295927-7788>