Date: Mon, 15 Apr 2024 17:58:23 +0100 From: void <void@f-m.fm> To: freebsd-ports@freebsd.org Subject: Re: holding rust at a particular version Message-ID: <Zh1cr9u3Df2E06Zt@int21h> In-Reply-To: <cc8ed2c43ab8e19c1dc16b9c7a394c8e@bsdforge.com> References: <Zh0srdWHPh9JlW8p@int21h> <20f77d23043622d68d6421bfdc9a1cc7@bsdforge.com> <CC1C6BE0-E7F4-4973-9FA7-087BB62B3ACC@freebsd.org> <cc8ed2c43ab8e19c1dc16b9c7a394c8e@bsdforge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 15, 2024 at 09:48:22AM -0700, Chris wrote: >I'm sorry to hear this. For the sake of clarity; Is this just my >ignorance for rust? >I have no difficulty accomplishing this task with other targets -- >perl, php, *SQL,... >So long as the *chosen* version is still available within the ports >tree. Granted; >this isn't a one-size-fits-all situation. Much the same as mixing >ports && packages. >But if carefully curated, has worked for me. Looking at the issue more widely, it seems that in ports that when rust updates, all rust-dependents are also updated to use that latest version, and I can't see of a way to override it except to take the local tree back to the 1.76 commit. Is this the right way? In bsd.default-versions.mk there is: ### # Possible values: rust, rust-nightly RUST_DEFAULT?= rust neither option would help in my case --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zh1cr9u3Df2E06Zt>